Branch: refs/heads/master
Home: https://github.com/jenkins-infra/jenkins.io
Commit: 98a0279e3d5f3c79bb21fb0f295cb424f49d067b
https://github.com/jenkins-infra/jenkins.io/commit/98a0279e3d5f3c79bb21fb0f295cb424f49d067b
Author: Tim Black <[email protected]>
Date: 2019-11-07 (Thu, 07 Nov 2019)
Changed paths:
M content/doc/book/pipeline-as-code.adoc
Log Message:
-----------
Update pipeline-as-code.adoc
Just wanting to make it clear that one can use "Pipeline as Code" (PaC) concept
outside the context of a Multibranch Pipeline or Organizational Folders job.
This tripped me up as I was learning about PaC.
Commit: f53e28027f9a8b6f9c308567295aa10917bb1ab9
https://github.com/jenkins-infra/jenkins.io/commit/f53e28027f9a8b6f9c308567295aa10917bb1ab9
Author: Mark Waite <[email protected]>
Date: 2019-11-07 (Thu, 07 Nov 2019)
Changed paths:
M content/doc/book/pipeline-as-code.adoc
Log Message:
-----------
Merge pull request #2631 from timblaktu/patch-1
Mention "Use SCM" option in normal Pipeline jobs in pipeline-as-code.adoc
Compare:
https://github.com/jenkins-infra/jenkins.io/compare/bbf6607ff55e...f53e28027f9a
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-commits/jenkins-infra/jenkins.io/push/refs/heads/master/bbf660-f53e28%40github.com.
