Closed Bug 1239263 Opened 6 years ago Closed 4 years ago

adding functionality to relengbot

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: vciobancai, Assigned: aselagea)

References

Details

No description provided.
Assignee: nobody → vlad.ciobancai
Created a pull request https://github.com/selenamarie/relengbot/pull/1 in order to add the following feature to relengbot. All the tests was made on my local computer and worked without any issue

:selenamarie can you please push the changes in to the master ?
Flags: needinfo?(sdeckelmann)
Merged!
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(sdeckelmann)
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
We will keep the bug open in order to keep tracking for the new features for relengbot
:selenamarie I would like to ask you when the changes will be pushed to heroku git repository ? 

Another question is, if we can enable the "Deployment method" process to use your project in github in stead of using the current heroku git repository ?

The following project https://github.com/selenamarie/relengbot ca be moved in the mozilla repository (https://github.com/mozilla)
Flags: needinfo?(sdeckelmann)
I found this plugin https://github.com/coderofsalvation/hubot-script-shellcmd and can be used in order to run the reconfig script. 

Coop I know we have discussed about this but I would like to ask you again, the reconfig should be run from heroku instance and all the "secret" stuff it will be stored only in heroku  or should we run the script from dev-master2 and to store the "secret" stuff on dev-master2?

The restriction it will be handle by hubot-auth and only a few persons will have access.
Flags: needinfo?(coop)
I don't care where it runs, honestly. 

dev-master2 is known to already have the flows in place to the masters/data sources (slavealloc) that are required to successfully run the script, and as such is the easiest place to run the script currently. That doesn't mean it's the proper place to run it forever.

If we want to go the heroku route, we'll need to setup the same flows, etc. We'll also need a process to create/update the containers, and suitable protection for the secrets inside.
Flags: needinfo?(coop)
I don't think the bot will have access from heroku to dev-master2 so I think it will be more OK to run the script from heroku instance.
:hal we will need your help in order to move the following project https://github.com/selenamarie/relengbot in to the github.com/mozilla in order to do not ping selenamarie for every pull request.
Flags: needinfo?(hwine)
Blocks: 1260793
No longer blocks: 1260793
Depends on: 1260793
(In reply to Vlad Ciobancai [:vladC] from comment #8)
> :hal we will need your help in order to move the following project
> https://github.com/selenamarie/relengbot in to the github.com/mozilla in
> order to do not ping selenamarie for every pull request.

See https://wiki.mozilla.org/Github#Forking_vs_Transferring for instructions on how to transfer the repository to mozilla. (Only a repository owner can initiate a transfer.)

Or, add folks as collaborators to the current repo location.
Flags: needinfo?(hwine)
(In reply to Hal Wine [:hwine] (use NI) from comment #9)
> (In reply to Vlad Ciobancai [:vladC] from comment #8)
> > :hal we will need your help in order to move the following project
> > https://github.com/selenamarie/relengbot in to the github.com/mozilla in
> > order to do not ping selenamarie for every pull request.
> 
> See https://wiki.mozilla.org/Github#Forking_vs_Transferring for instructions
> on how to transfer the repository to mozilla. (Only a repository owner can
> initiate a transfer.)
> 
> Or, add folks as collaborators to the current repo location.

Thank you, kmoir take care and create the following bug 1260793
Assignee: vciobancai → nobody
Assignee: nobody → aselagea
Repo has been moved.
Flags: needinfo?(sdeckelmann)
I don't see any activity on this bug for almost a year so I'll assume there weren't new features to relengbot added in the meantime. I'll go ahead and close this. Will follow-up with another bug if we need to. 

Relengbot currently lives under https://github.com/mozilla/relengbot
Status: REOPENED → RESOLVED
Closed: 6 years ago4 years ago
Resolution: --- → FIXED
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.