Re: Apache Beam - jenkins question
Hi, Jason Sorry for late response I was on vacations. I would like to send messages automatically to slack with Performance Analysis Daily Reports as described in this https://github.com/apache/beam/pull/5180: example report could be found on old apache beam slack https://apachebeam.slack.com/messages/CAB3W69SS/ Those messages were sent by me, and the missing thing is adding SLACK_WEBHOOK_URL which a token that allows post messages to slack. I will send it to you in separate message. So far I only have this token for an old apache beam slack generated, but in order to migrate it to new slack only credential in jenkins ui will need to be replaced. We can do it later, as I don't know who is responsible for managing the-asf.slack.com and can help me with that. 2018-04-28 1:31 GMT+02:00 Jason Kuster <jasonkus...@google.com>: > Thanks for the heads-up regarding the permissions. At this point I need > more information about the credentials we want to use -- Kamil, can you > provide more info? What is the purpose of the credentials you want to use > here? > > On Fri, Apr 27, 2018 at 3:50 PM Davor Bonaci <da...@apache.org> wrote: > >> Jason, you should now have all the permissions needed. (You should, >> however, evaluate whether this is a good place for it. Executors >> themselves, for example, might be an alternative.) >> >> On Fri, Apr 27, 2018 at 7:42 PM, Jason Kuster <jasonkus...@google.com> >> wrote: >> >>> See https://github.com/apache/beam/blob/master/.test-infra/ >>> jenkins/common_job_properties.groovy#L119 for an example of this being >>> done in practice to add the coveralls repo token as an environment variable. >>> >>> On Fri, Apr 27, 2018 at 12:41 PM Jason Kuster <jasonkus...@google.com> >>> wrote: >>> >>>> Hi Kamil, Davor, >>>> >>>> I think what you want is the Jenkins secrets feature (see >>>> https://support.cloudbees.com/hc/en-us/articles/203802500-Injecting- >>>> Secrets-into-Jenkins-Build-Jobs). Davor, I believe you are the only >>>> one with enough karma on Jenkins to access the credentials UI; once the >>>> credential is created in Jenkins it should be able to be set as an >>>> environment variable through the Jenkins job configuration (groovy files in >>>> $BEAM_ROOT/.test-infra/jenkins). Hope this helps. >>>> >>>> Jason >>>> >>>> On Thu, Apr 26, 2018 at 8:43 PM Davor Bonaci <da...@apache.org> wrote: >>>> >>>>> Hi Kamil -- >>>>> Thanks for reaching out. >>>>> >>>>> This is a great question for the dev@ mailing list. You may want to >>>>> share a little bit more why you need, how long, frequency of updates to >>>>> the >>>>> secret, etc. for the community to be aware how things work. >>>>> >>>>> Hopefully others on the mailing list can help you by manually putting >>>>> the necessary secret into the cloud settings related to the executors. >>>>> >>>>> Davor >>>>> >>>>> -- Forwarded message -- >>>>> From: Kamil Szewczyk <szewi...@gmail.com> >>>>> Date: Tue, Apr 24, 2018 at 12:21 PM >>>>> Subject: Apache Beam - jenkins question >>>>> To: da...@apache.org >>>>> >>>>> >>>>> Dear Davor >>>>> >>>>> I sent you a message on asf slack, wasn't sure how can I reach you. >>>>> >>>>> Anyway are you able to add secret (environment variable) to jenkins. >>>>> ?? >>>>> Or point me to a person that would be able to do that ? >>>>> >>>>> Kind Regards >>>>> Kamil Szewczyk >>>>> >>>>> >>>> >>>> -- >>>> --- >>>> Jason Kuster >>>> Apache Beam / Google Cloud Dataflow >>>> >>>> See something? Say something. go/jasonkuster-feedback >>>> <https://goto.google.com/jasonkuster-feedback> >>>> >>> >>> >>> -- >>> --- >>> Jason Kuster >>> Apache Beam / Google Cloud Dataflow >>> >>> See something? Say something. go/jasonkuster-feedback >>> <https://goto.google.com/jasonkuster-feedback> >>> >> >> > > -- > --- > Jason Kuster > Apache Beam / Google Cloud Dataflow > > See something? Say something. go/jasonkuster-feedback >
Re: Apache Beam - jenkins question
Thanks for the heads-up regarding the permissions. At this point I need more information about the credentials we want to use -- Kamil, can you provide more info? What is the purpose of the credentials you want to use here? On Fri, Apr 27, 2018 at 3:50 PM Davor Bonaci <da...@apache.org> wrote: > Jason, you should now have all the permissions needed. (You should, > however, evaluate whether this is a good place for it. Executors > themselves, for example, might be an alternative.) > > On Fri, Apr 27, 2018 at 7:42 PM, Jason Kuster <jasonkus...@google.com> > wrote: > >> See >> https://github.com/apache/beam/blob/master/.test-infra/jenkins/common_job_properties.groovy#L119 >> for an example of this being done in practice to add the coveralls repo >> token as an environment variable. >> >> On Fri, Apr 27, 2018 at 12:41 PM Jason Kuster <jasonkus...@google.com> >> wrote: >> >>> Hi Kamil, Davor, >>> >>> I think what you want is the Jenkins secrets feature (see >>> https://support.cloudbees.com/hc/en-us/articles/203802500-Injecting-Secrets-into-Jenkins-Build-Jobs). >>> Davor, I believe you are the only one with enough karma on Jenkins to >>> access the credentials UI; once the credential is created in Jenkins it >>> should be able to be set as an environment variable through the Jenkins job >>> configuration (groovy files in $BEAM_ROOT/.test-infra/jenkins). Hope >>> this helps. >>> >>> Jason >>> >>> On Thu, Apr 26, 2018 at 8:43 PM Davor Bonaci <da...@apache.org> wrote: >>> >>>> Hi Kamil -- >>>> Thanks for reaching out. >>>> >>>> This is a great question for the dev@ mailing list. You may want to >>>> share a little bit more why you need, how long, frequency of updates to the >>>> secret, etc. for the community to be aware how things work. >>>> >>>> Hopefully others on the mailing list can help you by manually putting >>>> the necessary secret into the cloud settings related to the executors. >>>> >>>> Davor >>>> >>>> -- Forwarded message -- >>>> From: Kamil Szewczyk <szewi...@gmail.com> >>>> Date: Tue, Apr 24, 2018 at 12:21 PM >>>> Subject: Apache Beam - jenkins question >>>> To: da...@apache.org >>>> >>>> >>>> Dear Davor >>>> >>>> I sent you a message on asf slack, wasn't sure how can I reach you. >>>> >>>> Anyway are you able to add secret (environment variable) to jenkins. ?? >>>> Or point me to a person that would be able to do that ? >>>> >>>> Kind Regards >>>> Kamil Szewczyk >>>> >>>> >>> >>> -- >>> --- >>> Jason Kuster >>> Apache Beam / Google Cloud Dataflow >>> >>> See something? Say something. go/jasonkuster-feedback >>> <https://goto.google.com/jasonkuster-feedback> >>> >> >> >> -- >> --- >> Jason Kuster >> Apache Beam / Google Cloud Dataflow >> >> See something? Say something. go/jasonkuster-feedback >> <https://goto.google.com/jasonkuster-feedback> >> > > -- --- Jason Kuster Apache Beam / Google Cloud Dataflow See something? Say something. go/jasonkuster-feedback
Re: Apache Beam - jenkins question
Jason, you should now have all the permissions needed. (You should, however, evaluate whether this is a good place for it. Executors themselves, for example, might be an alternative.) On Fri, Apr 27, 2018 at 7:42 PM, Jason Kuster <jasonkus...@google.com> wrote: > See https://github.com/apache/beam/blob/master/.test-infra/ > jenkins/common_job_properties.groovy#L119 for an example of this being > done in practice to add the coveralls repo token as an environment variable. > > On Fri, Apr 27, 2018 at 12:41 PM Jason Kuster <jasonkus...@google.com> > wrote: > >> Hi Kamil, Davor, >> >> I think what you want is the Jenkins secrets feature (see >> https://support.cloudbees.com/hc/en-us/articles/203802500-Injecting- >> Secrets-into-Jenkins-Build-Jobs). Davor, I believe you are the only one >> with enough karma on Jenkins to access the credentials UI; once the >> credential is created in Jenkins it should be able to be set as an >> environment variable through the Jenkins job configuration (groovy files in >> $BEAM_ROOT/.test-infra/jenkins). Hope this helps. >> >> Jason >> >> On Thu, Apr 26, 2018 at 8:43 PM Davor Bonaci <da...@apache.org> wrote: >> >>> Hi Kamil -- >>> Thanks for reaching out. >>> >>> This is a great question for the dev@ mailing list. You may want to >>> share a little bit more why you need, how long, frequency of updates to the >>> secret, etc. for the community to be aware how things work. >>> >>> Hopefully others on the mailing list can help you by manually putting >>> the necessary secret into the cloud settings related to the executors. >>> >>> Davor >>> >>> -- Forwarded message -- >>> From: Kamil Szewczyk <szewi...@gmail.com> >>> Date: Tue, Apr 24, 2018 at 12:21 PM >>> Subject: Apache Beam - jenkins question >>> To: da...@apache.org >>> >>> >>> Dear Davor >>> >>> I sent you a message on asf slack, wasn't sure how can I reach you. >>> >>> Anyway are you able to add secret (environment variable) to jenkins. ?? >>> Or point me to a person that would be able to do that ? >>> >>> Kind Regards >>> Kamil Szewczyk >>> >>> >> >> -- >> --- >> Jason Kuster >> Apache Beam / Google Cloud Dataflow >> >> See something? Say something. go/jasonkuster-feedback >> > > > -- > --- > Jason Kuster > Apache Beam / Google Cloud Dataflow > > See something? Say something. go/jasonkuster-feedback >
Re: Apache Beam - jenkins question
See https://github.com/apache/beam/blob/master/.test-infra/jenkins/common_job_properties.groovy#L119 for an example of this being done in practice to add the coveralls repo token as an environment variable. On Fri, Apr 27, 2018 at 12:41 PM Jason Kuster <jasonkus...@google.com> wrote: > Hi Kamil, Davor, > > I think what you want is the Jenkins secrets feature (see > https://support.cloudbees.com/hc/en-us/articles/203802500-Injecting-Secrets-into-Jenkins-Build-Jobs). > Davor, I believe you are the only one with enough karma on Jenkins to > access the credentials UI; once the credential is created in Jenkins it > should be able to be set as an environment variable through the Jenkins job > configuration (groovy files in $BEAM_ROOT/.test-infra/jenkins). Hope > this helps. > > Jason > > On Thu, Apr 26, 2018 at 8:43 PM Davor Bonaci <da...@apache.org> wrote: > >> Hi Kamil -- >> Thanks for reaching out. >> >> This is a great question for the dev@ mailing list. You may want to >> share a little bit more why you need, how long, frequency of updates to the >> secret, etc. for the community to be aware how things work. >> >> Hopefully others on the mailing list can help you by manually putting the >> necessary secret into the cloud settings related to the executors. >> >> Davor >> >> -- Forwarded message -- >> From: Kamil Szewczyk <szewi...@gmail.com> >> Date: Tue, Apr 24, 2018 at 12:21 PM >> Subject: Apache Beam - jenkins question >> To: da...@apache.org >> >> >> Dear Davor >> >> I sent you a message on asf slack, wasn't sure how can I reach you. >> >> Anyway are you able to add secret (environment variable) to jenkins. ?? >> Or point me to a person that would be able to do that ? >> >> Kind Regards >> Kamil Szewczyk >> >> > > -- > --- > Jason Kuster > Apache Beam / Google Cloud Dataflow > > See something? Say something. go/jasonkuster-feedback > -- --- Jason Kuster Apache Beam / Google Cloud Dataflow See something? Say something. go/jasonkuster-feedback
Re: Apache Beam - jenkins question
Hi Kamil, Davor, I think what you want is the Jenkins secrets feature (see https://support.cloudbees.com/hc/en-us/articles/203802500-Injecting-Secrets-into-Jenkins-Build-Jobs). Davor, I believe you are the only one with enough karma on Jenkins to access the credentials UI; once the credential is created in Jenkins it should be able to be set as an environment variable through the Jenkins job configuration (groovy files in $BEAM_ROOT/.test-infra/jenkins). Hope this helps. Jason On Thu, Apr 26, 2018 at 8:43 PM Davor Bonaci <da...@apache.org> wrote: > Hi Kamil -- > Thanks for reaching out. > > This is a great question for the dev@ mailing list. You may want to share > a little bit more why you need, how long, frequency of updates to the > secret, etc. for the community to be aware how things work. > > Hopefully others on the mailing list can help you by manually putting the > necessary secret into the cloud settings related to the executors. > > Davor > > -- Forwarded message -- > From: Kamil Szewczyk <szewi...@gmail.com> > Date: Tue, Apr 24, 2018 at 12:21 PM > Subject: Apache Beam - jenkins question > To: da...@apache.org > > > Dear Davor > > I sent you a message on asf slack, wasn't sure how can I reach you. > > Anyway are you able to add secret (environment variable) to jenkins. ?? > Or point me to a person that would be able to do that ? > > Kind Regards > Kamil Szewczyk > > -- --- Jason Kuster Apache Beam / Google Cloud Dataflow See something? Say something. go/jasonkuster-feedback
Fwd: Apache Beam - jenkins question
Hi Kamil -- Thanks for reaching out. This is a great question for the dev@ mailing list. You may want to share a little bit more why you need, how long, frequency of updates to the secret, etc. for the community to be aware how things work. Hopefully others on the mailing list can help you by manually putting the necessary secret into the cloud settings related to the executors. Davor -- Forwarded message -- From: Kamil Szewczyk <szewi...@gmail.com> Date: Tue, Apr 24, 2018 at 12:21 PM Subject: Apache Beam - jenkins question To: da...@apache.org Dear Davor I sent you a message on asf slack, wasn't sure how can I reach you. Anyway are you able to add secret (environment variable) to jenkins. ?? Or point me to a person that would be able to do that ? Kind Regards Kamil Szewczyk
