Yeah I wrote the original script and I intentionally made it easy for other projects to use (you'll just need to tweak some variables at the top). You just need somewhere to run it... we were using a jenkins cluster to run it every 5 minutes.
BTW - I looked and there is one instance where it hard cores the string "SPARK-", but that should be easy to change. I'm happy to review a patch that makes that prefix a variable. https://github.com/apache/spark/blob/master/dev/github_jira_sync.py#L71 - Patrick On Thu, May 14, 2015 at 8:45 AM, Josh Rosen <rosenvi...@gmail.com> wrote: > Spark PRs didn't always used to handle the JIRA linking. We used to rely > on a Jenkins job that ran > https://github.com/apache/spark/blob/master/dev/github_jira_sync.py. We > switched this over to Spark PRs at a time when the Jenkins GitHub Pull > Request Builder plugin was having flakiness issues, but as far as I know > that old script should still work. > > On Wed, May 13, 2015 at 9:40 PM, Nicholas Chammas < > nicholas.cham...@gmail.com> wrote: > >> There's no magic to it. We're doing the same, except Josh automated it in >> the PR dashboard he created. >> >> https://spark-prs.appspot.com/ >> >> Nick >> >> On Wed, May 13, 2015 at 6:20 PM Markus Weimer <mar...@weimo.de> wrote: >> >> > Hi, >> > >> > how did you set this up? Over in the REEF incubation project, we >> > painstakingly create the forwards- and backwards links despite having >> > the IDs in the PR descriptions... >> > >> > Thanks! >> > >> > Markus >> > >> > >> > On 2015-05-13 11:56, Ted Yu wrote: >> > > Subproject tag should follow SPARK JIRA number. >> > > e.g. >> > > >> > > [SPARK-5277][SQL] ... >> > > >> > > Cheers >> > > >> > > On Wed, May 13, 2015 at 11:50 AM, Stephen Boesch <java...@gmail.com> >> > wrote: >> > > >> > >> following up from Nicholas, it is >> > >> >> > >> [SPARK-12345] Your PR description >> > >> >> > >> where 12345 is the jira number. >> > >> >> > >> >> > >> One thing I tend to forget is when/where to include the subproject tag >> > e.g. >> > >> [MLLIB] >> > >> >> > >> >> > >> 2015-05-13 11:11 GMT-07:00 Nicholas Chammas < >> nicholas.cham...@gmail.com >> > >: >> > >> >> > >>> That happens automatically when you open a PR with the JIRA key in >> the >> > PR >> > >>> title. >> > >>> >> > >>> On Wed, May 13, 2015 at 2:10 PM Chandrashekhar Kotekar < >> > >>> shekhar.kote...@gmail.com> wrote: >> > >>> >> > >>>> Hi, >> > >>>> >> > >>>> I am new to open source contribution and trying to understand the >> > >> process >> > >>>> starting from pulling code to uploading patch. >> > >>>> >> > >>>> I have managed to pull code from GitHub. In JIRA I saw that each >> JIRA >> > >>> issue >> > >>>> is connected with pull request. I would like to know how do people >> > >> attach >> > >>>> pull request details to JIRA issue? >> > >>>> >> > >>>> Thanks, >> > >>>> Chandrash3khar Kotekar >> > >>>> Mobile - +91 8600011455 >> > >>>> >> > >>> >> > >> >> > > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org >> > For additional commands, e-mail: dev-h...@spark.apache.org >> > >> > >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
