[jbosstools-issues] [JBoss JIRA] (JBIDE-13526) Provide Jenkins-based mechanism for tagging published bits after they're promoted

[Nick Boldt (JIRA)]

Nick Boldt created JBIDE-13526:
----------------------------------

             Summary: Provide Jenkins-based mechanism for tagging published bits after they're promoted
                 Key: JBIDE-13526
                 URL: https://issues.jboss.org/browse/JBIDE-13526
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: Build/Releng, updatesite
    Affects Versions: 4.1.0.Alpha1
            Reporter: Nick Boldt
            Assignee: Max Rydahl Andersen
             Fix For: 4.1.0.Alpha2


Workflow for Project Leads of JBoss Tools 4.1:

a) spin jbosstools-<PROJECTNAME>_master [1] job (CI builds) (job checks github every 8hrs; if you want to spin more often, you can kick the job manually)
b) optionally, could push these builds to /integration/ folder once a week - talk to [~nickboldt] about setting up a weekly cron for your project

c) When codefreeze is declared, create stable branch (eg., jbosstools-4.1.0.Alpha2x - note "x" is appended)
d) edit existing jbosstools-<PROJECTNAME>_41 [2] job to point at new branch
e) spin _41 job; verify everything is blue
f) when satisfied with contents, publish to /development/ folder via jbosstools-promote job [3]
g) when promoted, use jbosstools-tag [4] job to push tag (eg., jbosstools-4.1.0.Alpha2 - note "x" is dropped) into the github repo, or tag manually like this:

{code}
git tag jbosstools-4.1.0.Alpha2
git push origin refs/tags/jbosstools-4.1.0.Alpha2
{code}

[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-base_master/
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-base_41/
[3] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/
[4] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-tag/

Questions or concerns?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira