[jbosstools-issues] [JBoss JIRA] (JBIDE-23151) script creation of PRs by generic user
Nick Boldt (JIRA)
issues at jboss.org
Tue Sep 13 12:02:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-23151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Boldt updated JBIDE-23151:
-------------------------------
Description:
Need the ability to create, submit, and merge PRs automatically as a generic user, so that changes to filesystem on download.jboss.org & devstudio.redhat.com (filemgmt) can be done automatically.
Spoke with [~akazakov] today to discuss how to proceed:
* new user "devstudio-release" for: jbdevstudio-website and jbosstools-downloads.jboss.org repos
* in future might also fork jbosstools-website repo so that changes to products.yaml can be automated too
* ideally, this would be a non-password (plaintext in config.xml = bad) authentication. github auth token? ssh key?
* maybe run this in isolation on wonka? that way less people have access to the config.xml of the job
* @Nick to explore getting more ssh keys for pushing to filemgmt.jboss.org
* @Nick to create user & start generating PRs for changes to dl.jb.o and ds.rh.c
was:
Need the ability to create, submit, and merge PRs automatically as a generic user, so that changes to filesystem on download.jboss.org & devstudio.redhat.com (filemgmt) can be done automatically.
Could use rhds-docker-jenkins user or some other shared user.
Will need assistance & approval from [~akazakov] in granting this user push rights on the two jbosstools-* and jbdevstudio-* repos.
> script creation of PRs by generic user
> --------------------------------------
>
> Key: JBIDE-23151
> URL: https://issues.jboss.org/browse/JBIDE-23151
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> Need the ability to create, submit, and merge PRs automatically as a generic user, so that changes to filesystem on download.jboss.org & devstudio.redhat.com (filemgmt) can be done automatically.
> Spoke with [~akazakov] today to discuss how to proceed:
> * new user "devstudio-release" for: jbdevstudio-website and jbosstools-downloads.jboss.org repos
> * in future might also fork jbosstools-website repo so that changes to products.yaml can be automated too
> * ideally, this would be a non-password (plaintext in config.xml = bad) authentication. github auth token? ssh key?
> * maybe run this in isolation on wonka? that way less people have access to the config.xml of the job
> * @Nick to explore getting more ssh keys for pushing to filemgmt.jboss.org
> * @Nick to create user & start generating PRs for changes to dl.jb.o and ds.rh.c
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list