thank you itchymuzzle
On Thursday, November 2, 2017 at 1:44:08 AM UTC-4, samy raj wrote:
>
> Hello All,
> I am looking for a simple project example which has non-java for a
> complete cycle of DevOps. I have a requirement for a project which has just
> many configuration files, Unix script files
> On 4. Nov 2017, at 13:02, Daniel Beck wrote:
>
> Look for the list entry just called 'Pipeline' (or search for
> pipeline-aggregator in the search box).
Oops -- used to be called workflow, so workflow-aggregator.
> Try to disable it. If the checkbox is disabled and you cannot, file a bug
>
> On 3. Nov 2017, at 18:22, CLOSE Dave wrote:
>
> Every one of the Pipeline plugins, all 23 of them, claim to be dependent
> on some other plugins. None offer the option to disable. The chain seems
> endless. And many of the plugins asserted to be dependent are ones I
> want to keep, such as Pip
Out of this thread but related to the attached screenshot, please obfuscate
the jenkins url :)
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+
2017-11-02 22:55 GMT+01:00 Ryan Hochstetler :
> Kris,
>
> I tried to travel down the same road, mounting a volume with the workspace
> directory into the slave containers as well as the master in order to
> expose the workspace contents post-build. The *jenkins way* to provide
> developer-visibil
Just to throw my 2 cents in, I guess it depends on what is meant by
self-signed - is that self-signed as in I've created a cert on my machine
and that's what I'm using, or is it "self-signed" in that its signed by a
CA that is internal to the organisation.
The former seems a bit of a strange case
