[
https://issues.jboss.org/browse/JBIDE-15918?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-15918:
---------------------------------------------
My thinking on this is to keep it simple is that we for every build should simply put a
tag in a separate repository, lets say owned by a jbosstools
user.
Then use a script or probably just a jenkins plugin to push a tag for each build and you
can then as a developer go check which exact commits was used for a build and decide to
move them over.
Jenkins has a user named
https://github.com/JBossJenkins which should be possible to use
to maintain such a separate "tagging" repo.
As an experiment I've created a user named "jbosstoolsci" (jbosstools is
already owned by our org) and have it forked some repos (
https://github.com/jbosstoolsci/
and JBossJenkins is a collaborator on these repos.
Lets see if we can get jenkins to tag those.
Could Jenkins perform tagging of its own repo?
----------------------------------------------
Key: JBIDE-15918
URL:
https://issues.jboss.org/browse/JBIDE-15918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.1.1.Beta1
Reporter: Nick Boldt
Priority: Minor
[~maxandersen] said:
{quote}
Project leads, please tag your projects!
{code}
co jbosstools-4.1.1.Beta1x
git tag jbosstools-4.1.1.Beta1
git push origin jbosstools-4.1.1.Beta1
{code}
{quote}
Then asked:
{quote}
Really would be nice if jenkins could just make such tags in its own repository and we
could move the exact commit over from the "build" repository to the master
repository.
{quote}
--
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