I would be surprised if there were such an argument. I'm not familiar with
the mercurial plugin, but I suspect it intends to choose the same hash.
Mark Waite
On Mon, May 1, 2017 at 6:53 AM Michael Rose wrote:
> This isn't a multi-branch pipeline job, just a normal pipeline job. The
> builds ar
Must be missing something but failing to see why merging a PR should
retrigger the builds of others.
Care to clarify?
Thanks
Le 1 mai 2017 10:43 PM, "Jeffrey" a écrit :
> So -- Ive reverted Jenkins to 2.46.2 latest patches and the behavior is
> the same.
>
> What I expect:
>
>1. Two open P
This plugin has an unfortunate known flaw - it will only spin up one
executor/node per label. If you have two jobs waiting to build with the
same label, it will build the first one, then kill after it's done, and
then start the next one. (Instead of creating two containers/tasks in
parallel) I'
Did you add all of us as moderators Tyler ?
On Sun, Apr 30, 2017 at 1:44 PM, Mark Waite
wrote:
> I agree with Baptiste. When I've checked on the moderator queue after a
> flurry of spam, more often than not I've found that someone else had
> already handled the messages which google groups had
So -- Ive reverted Jenkins to 2.46.2 latest patches and the behavior is the
same.
What I expect:
1. Two open PRs
2. Merge one PR to master
3. Master auto builds
4. Repo is scanned and the other PR builds. This is still not happening.
Any help much appreciated.
On Friday, April
In response to our on-going battle against spam, we have grown the Google Group
moderations teams for jenkinsci-dev@ and jenkinsci-users@. With more
moderators, this means that we can enable "New poster" moderation.
What this means is that, until further notice, first-time posters to these
mailin
Here's our current web.config file for IIS:
http://localhost:8080/{R:1}"; />
Did you every find a solution or come to understand why its like this?
On Sunday, November 13, 2016 at 1:05:14 PM UTC-5, Jonathan Hodgson wrote:
>
> Ok, so having got my script working, I decided to move part of it into a
> shared library as per the section marked Define more structured DSL
> her
So I misunderstood the mechanism of PR build where the target branch is not
merged into the destination branch before build
what is the benefit of auto build both merge and pr for every new commit?
I can understand the benefit before issuing the PR, but from my experience
ppl usually issue PR
I'm not sure if this is useful information, but we see this in the
jenkins-stderr logs when browsing to the Manage Jenkins page:
01-May-2017 12:10:39.038 WARNING [Handling GET
/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testForReverseProxySetup/https:/
our.server.name/manage/
Hi, Stephen. Thanks for your reply.
I'm not sure about X-Forwarded-Host. I think we tried that, but I'll have
to check with our SA, and he's not here right now. I'll get back here as
soon as I find out.
We did try a couple of iterations where we tried to redirect
https://our.server.name/ to ht
dan,
i understand that you're using the bitbucket branch source plugin, you
introduce a syntax error into the mainline branch (let's call it master),
and you submit a pull request for a different branch (let's call it
feature/new-hotness) that wasn't based off this bad master branch. your
mast
On Mon 1 May 2017 at 16:13, Terry Lacy wrote:
> Is there other information I could supply that would help?
>
> Alternatively, has anyone successfully set up Jenkins behind IIS with a
> setup similar to that described below *without* getting the bad proxy
> message? Would you be willing to share y
Is there other information I could supply that would help?
Alternatively, has anyone successfully set up Jenkins behind IIS with a
setup similar to that described below *without* getting the bad proxy
message? Would you be willing to share your setup?
So far, things seem to work fine despite th
On my side, the service needed to be Local System to be able to launch
properly, which prevent GUI and graphical context to be run inside the
service. Since I needed the GUI context for some unit test (OpenGL unit
test was problematic), I had to change the service user for a local user.
That pr
This isn't a multi-branch pipeline job, just a normal pipeline job. The
builds are definitely running with the same hash. Here is the code for my
SCM step:
stage('SCM: Update rt') {
checkout([$class: 'MercurialSCM',
credentialsId: 'NightlybuildSSHKey',
source
You say that you're getting a response status code 401, but you don't say
what is returning that response status code. Are you checking the job
status with a call to the Jenkins REST API, and it is returning 401? Is
the job attempting to push to Nexus and that is reporting 401? Is the job
a mave
Hi..
I am configured one project in jenkins, and source code is there in
Bitbucket and packages are there in Nexus.
while i triggered build i am getting Response status code does not indicate
success: 401 (Unauthorized) issue,
but same thing if i build from command prompt, its working fine, if it
Hi
I'm using Jenkins 2.57 with installing Windows Installer.
I can start Windows Service for Jenkins manually.
But it doesn't start automatically.
How do I make it start automatically?
Regards.
Masaru.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Us
19 matches
Mail list logo
