[PIPE2D-544] For releases, apply tags to each repository Created: 10/Apr/20  Updated: 05/Jan/21  Resolved: 23/Apr/20

Status: Done
Project: DRP 2-D Pipeline
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Normal
Reporter: hassan Assignee: price
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to PIPE2D-546 Generate release change log Done
relates to PIPE2D-545 Inconsistent eups versions assigned t... Won't Fix
relates to PIPE2D-576 Generate changelog for DRP releases Done
Story Points: 1
Sprint: 2DDRP-2021 A
Reviewers: hassan

 Description   

Currently when making a 2D DRP release, only the git repository pfs_pipe2d is tagged. To enable convenient look-up of all the commits across all 2D DRP repositories related to a release, please provide a script or equivalent to apply the same tag to the appropriate commit on each 2D DRP repository (drp_pfs_data, datamodel, obs_pfs, drp_stella, pfs_pipe2d.



 Comments   
Comment by price [ 15/Apr/20 ]

I added a new script that will tag all packages and then trigger the Jenkins release script.

Jenkins is now triggered by this script; it doesn't poll git looking for tags any more.

Comment by price [ 23/Apr/20 ]

Merged to master.

Generated at Sat Feb 10 15:54:42 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.