Details
-
Type:
Story
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: Developer Infrastructure
-
Labels:None
-
Team:Alert Production
Description
I just broke ci_hsc with the merge of DM-8232 and didn't realize it because I didn't run ci_hsc on Jenkins pre-merge.
In this ticket, I'm suggesting two things:
- We create a pre-merge Jenkins target that builds all the things we think should be run before a merge happens
- We add ci_hsc to that pre-merge target
(Note that I'm not sure I'm using the word target correctly here, but hopefully you get my meaning)
We haven't been running ci_hsc pre-merge because it takes about thirty min to run, but I think if we make it clear that can be done in parallel with the review it shouldn't be too bad.
Attachments
Issue Links
- mentioned in
-
Page Loading...
Activity
Unfortunately, I'm stepping down from the project before that thinking can take place.
I'd like to at least write some clear guidelines for what all the various CI packages are, and what users are required/expected/encouraged to run before a merge. I'll grab this so I can do some thinking about it.