Addshore added a comment.

  In T272130#6792307 <https://phabricator.wikimedia.org/T272130#6792307>, 
@sbassett wrote:
  
  > @Ladsgroup @Michael -  The #security-team 
<https://phabricator.wikimedia.org/tag/security-team/> discussed this task this 
morning.  Is the plan to pull from github for deployments upon Wikimedia 
production hardware?  If so, I believe #sre 
<https://phabricator.wikimedia.org/tag/sre/> does not allow for that.
  
  Not quite, here is the summary
  
  So, this will be deployed via a build in jenkins (ideally), so that it uses 
the same process and the query gui.
  This is just about to be created by the campsite as a push button trigger in 
https://phabricator.wikimedia.org/T210286
  I guess it's only for a similar job to exist fetching code from github to 
create the build that would then be deployed?
  
  Another alternative would be github actions to make the build and push a 
change to gerrit?
  I don't see a big difference between the two as either way the build is 
triggered by a human, and the change is still 2ed by a human.
  The one difference would be that npm install is running in a different place 
for each.
  
  > For original development, it made sense since the CI was pretty easy to 
setup
  
  I don't think there is anything that different to normal CI things for this 
repository that would make it hard to run in jenkins (but I could be wrong)

TASK DETAIL
  https://phabricator.wikimedia.org/T272130

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Addshore
Cc: Addshore, sbassett, Michael, Ladsgroup, Jakob_WMDE, DannyS712, Aklapper, 
Lydia_Pintscher, Devnull, Akuckartz, Dsharpe, Nandana, Lahi, Gq86, 
GoranSMilovanovic, QZanden, EBjune, LawExplorer, _jensen, rosalieper, 
Scott_WUaS, Wong128hk, Luke081515, Wikidata-bugs, aude, Bawolff, csteipp, 
Mbch331, Rxy, Jay8g, Krenair, chasemp
_______________________________________________
Wikidata-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to