infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Harui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-17540) Allow Jenkins jobs to commit/push to SVN and Git
Date Thu, 03 Jan 2019 23:33:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-17540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733630#comment-16733630
] 

Alex Harui commented on INFRA-17540:
------------------------------------

[~rvs] The Royale process would have the bot push changes to pom.xml files both via some Ant
scripts that modify the file, and via Maven's release plugin.  So, not really logical code,
just version numbers and maybe some other configuration information.

> Allow Jenkins jobs to commit/push to SVN and Git
> ------------------------------------------------
>
>                 Key: INFRA-17540
>                 URL: https://issues.apache.org/jira/browse/INFRA-17540
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Buildbot, Jenkins
>            Reporter: Alex Harui
>            Priority: Major
>
> Creating this issue so we don't lose track:
> Per this thread: https://lists.apache.org/thread.html/6f960908e2065841d638f77d4028241f5b91f5b5bcd98ddd36d43295@%3Cbuilds.apache.org%3E
> It would be great if Jenkins jobs could commit/push to SVN and/or Git.
> I think if there was a "user" in LDAP called buildbot or build@a.o, then projects could
see which commits are coming from builds.a.o.
> Maven builds might also require allowing this "user" to PGP sign as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message