Thanks guys, I must have made a typo somewhere... - I did a clean setup and
tried the whole ting again - now it works!
Many thanks!
> On 20 Nov 2018, at 06:05, Richard Bywater wrote:
>
> I also just today set the password in Visual Code Studio to be my API token
> and it worked like a charm.
I also just today set the password in Visual Code Studio to be my API token
and it worked like a charm.
Richard.
On Tue, 20 Nov 2018, 9:36 AM Christopher Orr, wrote:
> FWIW, I had no problems setting it up with an API token last week (in
> place of a password), on a Jenkins instance that uses
Hi there,
I've got some questions regarding extending the provided
pipeline/jenkins-infra in the https://ci.jenkins.io to enable:
- BATS in the linux agent
- DinD within the Jenkinsfile.
This is more precisely to enable the Validation of the JCASC Demos: see the
in-progress
PoC
FWIW, I had no problems setting it up with an API token last week (in place of
a password), on a Jenkins instance that uses the Google Login plugin for
authentication.
On Mon, 19 Nov 2018, at 13:29, domi wrote:
> Unfortunately this does not seem to work :(
>
> > On 16 Nov 2018, at 20:18,
Hello,
When Trusted.ci built and released the docker image for jenkins 2.152 based on
java 11, the script also released 19 older docker images which weren't tested
on java 11.
This concerns version from 2.135 to 2.147.
Why do we always build the latest 20 release instead of just the latest
Unfortunately this does not seem to work :(
> On 16 Nov 2018, at 20:18, Jesse Glick wrote:
>
> On Fri, Nov 16, 2018 at 8:12 AM domi wrote:
>> I really like the way I can validate my Jenkinsfile from within VS Code now:
>> https://jenkins.io/blog/2018/11/07/Validate-Jenkinsfile/
>>
>> But how
Hello,
I just commented in the PR.
On Fri, 9 Nov 2018 at 15:51, Heiko Bennewitz
wrote:
> Hello,
>
> I’d like to request commit access for
> https://github.com/jenkinsci/lockable-resources-plugin.
>
> As suggested I waited one week for answer on my pull request.
>
>
>
> Me on github: haithir
>
Given the regressions the original change caused, I recommend that we include
JENKINS-54551.
We did the same towards the 2.152 weekly while we wait for more feedback on the
better fix (PR 3761).
> On 12. Nov 2018, at 10:32, Oliver Gondža wrote:
>
> Backporting has started and the RC is
> On 19. Nov 2018, at 10:34, Sameer wrote:
>
> I have updated nirmata-plugin to v1.0.9 yesterday however I don't see it
> being available in the Update Center post 12 hrs
> (https://repo.jenkins-ci.org/releases/io/jenkins/plugins/nirmata/1.0.9/).
>
Thanks, we're tracking the cause as
Hi,
I have updated nirmata-plugin to v1.0.9 yesterday however I don't see it
being available in the Update Center post 12 hrs
(https://repo.jenkins-ci.org/releases/io/jenkins/plugins/nirmata/1.0.9/).
Thanks,
Sameer
--
You received this message because you are subscribed to the Google Groups
10 matches
Mail list logo