You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sh "java -jar target/update-dois-*-jar-with-dependencies.jar $ConfigFile"
68
49
}
69
50
}
70
51
}
71
52
}
72
53
// This stage takes the generated report file and sends it to the curator overseeing release.
73
54
// Before moving onto the next stage of UpdateDOIs, their confirmation that the contents of the report file are correct is needed.
74
-
/*
75
-
stage('Send email of updateable DOIs to curator'){
55
+
stage('Main: Send email of updateable DOIs to curator'){
76
56
steps{
77
57
script{
78
-
emailext (
79
-
body: "This is an automated message. Please review the attached file of Pathway DOIs to be updated and confirm they are correct with the developer running release. Thanks!",
80
-
to: '$DEFAULT_RECIPIENTS',
81
-
subject: "UpdateDOIs List for v${currentRelease}",
82
-
attachmentsPattern: "**///doisToBeUpdated-v${currentRelease}.txt" <- This pattern (**/) messses up multi-line comments. When uncommenting, remove 2/3 backslashes before 'doisToBeUpdated'
def emailSubject ="UpdateStableIdentifiers complete & UpdateDOIs List for v${releaseVersion}"
61
+
def emailBody ="This is an automated message: UpdateDOIs has completed a test run to determine which Pathway DOIs will be updated in the \'${env.RELEASE_CURRENT_DB}\' and \'${env.GK_CENTRAL_DB}\' databases. Please review the attached ${doisToBeUpdatedFile} file and let the developer running Release know if they look correct. \n\nThanks!"
// UpdateDOIs should pause at this stage until the curator confirms the report file is correct. Once they do, respond with 'yes' to the user input form that Jenkins brings up.
89
69
stage('User Input Required: Confirm DOIs'){
90
70
steps{
91
71
script{
92
-
// This brings up a user input form, asking for confirmation that the curator overseeing release approves of the report file they received.
72
+
def releaseVersion = utils.getReleaseVersion()
73
+
// This asks user to confirm that the UpdateDOIs.report file has been approved by Curation.
93
74
def userInput = input(
94
-
id: 'userInput', message: "Has a curator confirmed that the list of DOIs to be updated in doisToBeUpdated-v${currentRelease}.txt is correct? (yes/no)",
75
+
id: 'userInput', message: "Proceed once \'doisToBeUpdated-v${releaseVersion}.txt\' has been approved by curation. It should have been sent in an email after the test run step.",
// This sends an email notifying the mailing list that both the UpdateStableIdentifiers and UpdateDOIs steps have completed. This indicates that gk_central can be reopened.
121
+
stage('Post: Send completion email') {
122
+
steps{
123
+
script{
124
+
def releaseVersion = utils.getReleaseVersion()
125
+
def emailSubject ="UpdateStableIdentifier and UpdateDOIs complete for v${releaseVersion}"
126
+
def emailBody ="Hello,\n\nThis is an automated message from Jenkins regarding an update for v${releaseVersion}: Both UpdateStableIdentifiers and UpdateDOIs steps have completed. ${env.GK_CENTRAL_DB} can likely be reopened, but Curation should get \'Human\' confirmation before doing so. \n\nThanks!"
Copy file name to clipboardExpand all lines: README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -8,8 +8,8 @@ More technically, it will find all 'Pathway' instances with a 'doi' attribute th
8
8
from the instance's 'stableIdentifier' attribute.
9
9
10
10
New features and tests have been implemented for this iteration of UpdateDOIs:
11
-
- Runtime tests ensure conchordance of the instance's being updated in the Test Reactome and GK Central databases
12
-
- Users can provide a report file (UpdateDOIs.report) of DOIs that are expected to be updated. It can be created from the data found <ahref="https://docs.google.com/spreadsheets/d/1KtZ_Z3rvBELroubmeO1ai5otbsS26QpXZn6au-oSCWw/edit#gid=1011530219">here</a>. This is explained further in <ahref="https://github.com/reactome/data-release-pipeline/new/develop/update-dois#updatedoisreport">UpdateDOIs.report</a> section.
11
+
- Runtime tests ensure concordance of the instance's being updated in the Test Reactome and GK Central databases
12
+
- Users can provide a report file (UpdateDOIs.report) of DOIs that are expected to be updated. It can be created from the data found <ahref="https://docs.google.com/spreadsheets/d/1KtZ_Z3rvBELroubmeO1ai5otbsS26QpXZn6au-oSCWw/edit#gid=1011530219">here</a>. This is explained further in <ahref="#updatedoisreport">UpdateDOIs.report</a> section.
13
13
- If the report has been provided, the script will report any unexpected behaviour and attempt to suggest to the user why it happened
14
14
15
15
<h2>Configuration</h2>
@@ -66,7 +66,7 @@ To use this feature, follow these steps:
66
66
2) Create a new 'UpdateDOIs.report' file or remove the contents of the old one found at `src/main/resources`
67
67
3) For each row of the spreadsheet that contains a new curation:
68
68
- Prepend each 'stableID' with "10.3180/" to create the new DOI (eg: 10.3180/R-HSA-123456789.1)
69
-
- Copy into UpdateDOIs.report the new DOI and 'name', seperated by a comma (eg: 10.3180/R-HSA-123456789.1,Reactome Annotation Example)
69
+
- Copy into UpdateDOIs.report the new DOI and 'name', separated by a comma (eg: 10.3180/R-HSA-123456789.1,Reactome Annotation Example)
70
70
4) If you created a new new UpdateDOIs.report file, move it to the `src/main/resources` folder.
0 commit comments