Closed Bug 1398916 Opened 7 years ago Closed 7 years ago

automate merging for staging releases

Categories

(Release Engineering :: Release Automation: Other, enhancement)

Product:
Release Engineering
Component:
Release Automation: Other
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: kmoir, Assigned: kmoir)

References

Details

Attachments

(1 file)

pull request
50 bytes, text/x-github-pull-request
mtabara
: feedback+
Details | Review 
There are several manual steps to merge code for staging releases.  We should see automate this so that is this is more automated

https://github.com/mozilla/releasewarrior/blob/master/how-tos/setup-staging-release.md
Blocks: 1398909
No longer blocks: 1397762
Assignee: nobody → kmoir
Depends on: 1401572
No longer depends on: 1401572
Looking at the merge scripts this morning, it seems like it would be beneficial to have a dedicated machine for staging releases, like we do for the merge day scripts, perhaps the same machine.

https://bugzilla.mozilla.org/show_bug.cgi?id=1400015#c3
Attached file pull request — 

    
  

        Attachment #8917146 -
        Flags: feedback?(mtabara)

    
    

    
  
Comment on attachment 8917146 [details] [review]
pull request

Made my comments in the PR.

        Attachment #8917146 -
        Flags: feedback?(mtabara) → feedback+

    
    

    
  
I'm going to close this bug but mark 1400015 (optimize merge day environment as blocking 1398909 (staging releases tracking bug) to address the issues in comment #1 above
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: