-
Notifications
You must be signed in to change notification settings - Fork 31
Fix miscellaneous ci issues #78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
e0abca6
9c138f8
72e9dc6
d77c2a2
d167180
a24e93a
d5c8456
1ee74e5
cfd4a0b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,6 @@ | ||
| jobs: | ||
| - job: Windows | ||
| - job: Windows_build | ||
| displayName: Windows build | ||
|
Comment on lines
+2
to
+3
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please revert this. Make it
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I was copying the So maybe upstream will eventually take this? I do think they want parallel testing on Windows x64. (I think they might be more likely to take it if it is separated out from the "move lots of stuff to templates" changes. But I'm not them so I can't read their minds about that. It would be most welcome if they would comment on our PR.)
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This job is called on other files too like Release job. After all, it is just a name, I don't think it is important. 😄 If you want to change it you change it everywhere. |
||
| dependsOn: GetReleaseVersion | ||
| timeoutInMinutes: 180 | ||
| strategy: | ||
|
|
@@ -71,7 +72,8 @@ jobs: | |
| condition: and(succeeded(), eq(variables['IsReleaseBranch'], 'true')) | ||
|
|
||
| - job: Windows_RendererTests | ||
| dependsOn: Windows | ||
| displayName: Windows | ||
| dependsOn: Windows_build | ||
|
Comment on lines
+75
to
+76
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please revert this. |
||
| timeoutInMinutes: 180 | ||
| strategy: | ||
| maxParallel: 2 | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason that MAIN_REPO is missing here? Just want to check if we haven't missed it.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The script authors didn't use "the name of the main repo" anywhere in the script. I suppose they had no need for it.
(Where they use the string
'atom', they mean "the repo owner"; the org/user whose account the [nightly] repo is under.)And the linter gets upset if you define a variable and don't use it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/atom-ide-community/atom/blob/23ad7fe8575e8419e08ede6e2ebe110e8708e725/script/vsts/get-release-version.js#L32
This is the only place in the file any of these vars is needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By the way, from reading that line, it appears if our Nightly repo goes stale, and lacks recent tags, our auto drafts of releases (if we use that feature) will not advance their version number. So we would perhaps have to manually fix the suggested version number?
Something to keep in mind. Some of Atom's release CI steps are very interconnected with the Nightly repo.