Re: build for pull request

2014-01-09 Thread Hangsu Ma
, 2014 at 1:39 PM, Hangsu Ma > > wrote: > > Do you have a document for the steps? i am not familiar with Jenkins > build process. > > This is more about using GitHub generally. > > > I tried to push the change into a new remote branch on > jenkinsci/jenkins, &g

Re: build for pull request

2014-01-09 Thread Hangsu Ma
On Thu, Jan 9, 2014 at 11:24 AM, Hangsu Ma > > wrote: > > Is there anyway to rebuild the pull request again? > > Just make sure the master branch is updated in your repo, then > > git merge master > > and push the merge to your feature branch. The merge commit

build for pull request

2014-01-09 Thread Hangsu Ma
Hi Community, I sent a pull request 6 monthes ago: [FIXED JENKINS-14713] make Cancel independent from Build permission https://github.com/jenkinsci/jenkins/pull/882 There were a build with few failing unit tests, which were failing before the build already, i believe they are not related to my c

Re: Pull Request: 882 seperate Cancel permission from Build permission for JENKINS-14713

2013-12-20 Thread Hangsu Ma
uest? > > Regards, > Nickolay > > среда, 24 июля 2013 г., 20:40:04 UTC+4 пользователь Hangsu Ma написал: > >> Hi All, >> >> Please let me know what do you think on this! >> >> *The reasons:* >> >>- On Jenkins security authorization matrix

unit test failure on jenkins_main_trunk build for pull request

2013-11-05 Thread Hangsu Ma
Hi All, I noticed there is a build: https://jenkins.ci.cloudbees.com/job/core/job/jenkins_main_trunk/1324/ for my pull request, and there are 3 units failing. I dont think these unit tests are related to the pull request, is there any thing i need to do here? -- You received this message becaus

Pull Request: 882 seperate Cancel permission from Build permission for JENKINS-14713

2013-07-24 Thread Hangsu Ma
Hi All, Please let me know what do you think on this! *The reasons:* - On Jenkins security authorization matrix, Build and Cancel are listed as different items in same category, this normally implies they are independent permissions. But the current behavior is: Build permission i