Site updated to cd976fd

2017/08/08/gocd-elastic-agents-benefits.html

@@ -107,7 +107,7 @@ <h3 id="save-time-reduce-effort">1. Save time, reduce effort</h3>
 
 <p>Before elastic agents, if we wanted to test something new that needed different hardware or software, we needed to provision build machines, and have the relevant software installed on these agents. Then if we chose to not keep the change, we also had to decommission the machines. It was time consuming  to do all of that, and took the focus away from development.</p>
 
-<p>Using elastic agents, we can apply the idea behind <a href="https://martinfowler.com/bliki/ImmutableServer.html">ImmutableServer</a> to our build machines. We now <a href="https://hub.docker.com/r/gocdcontrib/gocd-dev-build/builds/">build an operating system image</a> with all the required software (with the versions we need). This allowed us to operate quickly, and experiment without the worry of managing hardware.</p>
+<p>Using elastic agents, we can apply the idea behind <a href="https://martinfowler.com/bliki/ImmutableServer.html">ImmutableServer</a> to our build machines. We now <a href="https://hub.docker.com/r/gocddev/gocd-dev-build/tags">build an operating system image</a> with all the required software (with the versions we need). This allowed us to operate quickly, and experiment without the worry of managing hardware.</p>
 
 <h3 id="less-pain-and-overhead">2. Less pain and overhead</h3>
 

2017/08/08/gocd-elastic-agents-benefits/index.html

@@ -107,7 +107,7 @@ <h3 id="save-time-reduce-effort">1. Save time, reduce effort</h3>
 
 <p>Before elastic agents, if we wanted to test something new that needed different hardware or software, we needed to provision build machines, and have the relevant software installed on these agents. Then if we chose to not keep the change, we also had to decommission the machines. It was time consuming  to do all of that, and took the focus away from development.</p>
 
-<p>Using elastic agents, we can apply the idea behind <a href="https://martinfowler.com/bliki/ImmutableServer.html">ImmutableServer</a> to our build machines. We now <a href="https://hub.docker.com/r/gocdcontrib/gocd-dev-build/builds/">build an operating system image</a> with all the required software (with the versions we need). This allowed us to operate quickly, and experiment without the worry of managing hardware.</p>
+<p>Using elastic agents, we can apply the idea behind <a href="https://martinfowler.com/bliki/ImmutableServer.html">ImmutableServer</a> to our build machines. We now <a href="https://hub.docker.com/r/gocddev/gocd-dev-build/tags">build an operating system image</a> with all the required software (with the versions we need). This allowed us to operate quickly, and experiment without the worry of managing hardware.</p>
 
 <h3 id="less-pain-and-overhead">2. Less pain and overhead</h3>
 

2017/10/10/architecting-continuous-delivery.html

@@ -120,7 +120,7 @@ <h3 id="componentization-via-libraries"><strong>Componentization via Libraries</
 
 <p>But when there are multiple functional teams working on the same repo, the biggest payoff comes when you can separate out each team's work into components to be managed in their own repos.</p>
 
-<p>One large-scale Open Source project doing this is the <a href="https://wiki.openmrs.org/display/docs/Modules">OpenMRS</a> application where independent modules are wired up together in the application runtime. A component in this case is a binary dependency that includes end-to-end functionality of a module including the UI. Deployment of a component can be managed on the deployment pipeline and means upgrading the component version on the parent application.</p>
+<p>One large-scale Open Source project doing this is the <a href="https://openmrs.org">OpenMRS</a> application where independent modules are wired up together in the application runtime. A component in this case is a binary dependency that includes end-to-end functionality of a module including the UI. Deployment of a component can be managed on the deployment pipeline and means upgrading the component version on the parent application.</p>
 
 <p>On one of our projects where we saw the pains of a large team working on a monolithic content management system (CMS) codebase in Java, we started to break out components under active development into separate repos. For example, the search functionality was separated out. Then, everything related to search - from UI to backend code - could be developed on a much smaller codebase. The binary artifact, in this case a JAR file, could then be plugged in as a runtime dependency on the application. We then had a small test suite on the main application build pipeline to validate that the component worked well within the application boundaries.</p>
 

2017/10/10/architecting-continuous-delivery/index.html

@@ -120,7 +120,7 @@ <h3 id="componentization-via-libraries"><strong>Componentization via Libraries</
 
 <p>But when there are multiple functional teams working on the same repo, the biggest payoff comes when you can separate out each team's work into components to be managed in their own repos.</p>
 
-<p>One large-scale Open Source project doing this is the <a href="https://wiki.openmrs.org/display/docs/Modules">OpenMRS</a> application where independent modules are wired up together in the application runtime. A component in this case is a binary dependency that includes end-to-end functionality of a module including the UI. Deployment of a component can be managed on the deployment pipeline and means upgrading the component version on the parent application.</p>
+<p>One large-scale Open Source project doing this is the <a href="https://openmrs.org">OpenMRS</a> application where independent modules are wired up together in the application runtime. A component in this case is a binary dependency that includes end-to-end functionality of a module including the UI. Deployment of a component can be managed on the deployment pipeline and means upgrading the component version on the parent application.</p>
 
 <p>On one of our projects where we saw the pains of a large team working on a monolithic content management system (CMS) codebase in Java, we started to break out components under active development into separate repos. For example, the search functionality was separated out. Then, everything related to search - from UI to backend code - could be developed on a much smaller codebase. The binary artifact, in this case a JAR file, could then be plugged in as a runtime dependency on the application. We then had a small test suite on the main application build pipeline to validate that the component worked well within the application boundaries.</p>
 

2018/11/30/deployment-frequency.html

@@ -115,7 +115,7 @@ <h2 id="an-example-how-to-use-deployment-frequency">An Example: How to Use Deplo
   <li>Is your end-to-end lead time from commit to deployment too long?</li>
   <li>Do you have builds that fail very often?</li>
   <li>Do you have flaky tests? If tests are flaky consider understanding which ones are the biggest problem and <a href="https://gauge.org/2018/10/23/taiko-beta-reliable-browser-automation/">addressing the root cause</a>.</li>
-  <li>Are you <a href="https://kanbanize.com/blog/stop-the-line/">stopping the line</a> to address other problems?</li>
+  <li>Are you <a href="https://businessmap.io/blog/stop-the-line">stopping the line</a> to address other problems?</li>
   <li>Do you have long-lived feature branches or pull-requests which are not merged often?. Very often we see the development team working hard on their branches, but the business won’t see that value until the changes are deployed.  If your problem is that you have work going on in long-lived branches, consider feature toggles and <a href="https://trunkbaseddevelopment.com/">trunk based development</a>.</li>
 </ul>
 
@@ -130,6 +130,7 @@ <h2 id="summary">Summary</h2>
   <a href="../../../analytics.html" class="cornered-banner_cta">SIGN UP</a>
 </div>
 
+
       </main>
     </div>
     <div class="col-md-3">

2018/11/30/deployment-frequency/index.html

@@ -115,7 +115,7 @@ <h2 id="an-example-how-to-use-deployment-frequency">An Example: How to Use Deplo
   <li>Is your end-to-end lead time from commit to deployment too long?</li>
   <li>Do you have builds that fail very often?</li>
   <li>Do you have flaky tests? If tests are flaky consider understanding which ones are the biggest problem and <a href="https://gauge.org/2018/10/23/taiko-beta-reliable-browser-automation/">addressing the root cause</a>.</li>
-  <li>Are you <a href="https://kanbanize.com/blog/stop-the-line/">stopping the line</a> to address other problems?</li>
+  <li>Are you <a href="https://businessmap.io/blog/stop-the-line">stopping the line</a> to address other problems?</li>
   <li>Do you have long-lived feature branches or pull-requests which are not merged often?. Very often we see the development team working hard on their branches, but the business won’t see that value until the changes are deployed.  If your problem is that you have work going on in long-lived branches, consider feature toggles and <a href="https://trunkbaseddevelopment.com/">trunk based development</a>.</li>
 </ul>
 
@@ -130,6 +130,7 @@ <h2 id="summary">Summary</h2>
   <a href="../../../../analytics.html" class="cornered-banner_cta">SIGN UP</a>
 </div>
 
+
       </main>
     </div>
     <div class="col-md-3">

2023/02/13/gocd-project-status.html

@@ -158,7 +158,7 @@ <h3 id="is-it-risky-to-continue-to-use-gocd-from-a-security-standpoint">Is it ri
   <li>We believe GoCD was built with solid security principles in mind that have generally stood the test of time.</li>
   <li>Software dependencies incorporated within GoCD are <em>generally</em> still under active development, and thus being
 patched/updated. These are being incorporated into new GoCD releases without major issue.</li>
-  <li>GoCD runs on and is built/test using modern, maintained language runtimes (Java 17 LTS, NodeJS 18 LTS, Ruby 3.1)</li>
+  <li>GoCD runs on and is built/test using modern, maintained language runtimes (Java 17 LTS, NodeJS 20 LTS, Ruby 3.1)</li>
   <li>GoCD continues to have good compatibility with latest operating systems, which can be extended to its supported
 <a href="../../../download.html">Docker images</a>.</li>
 </ul>
@@ -179,7 +179,7 @@ <h3 id="is-it-risky-to-continue-to-use-gocd-from-a-security-standpoint">Is it ri
 Keeping on top of all of these requires non-trivial effort, and is likely not indefinitely sustainable with the current
 contributor/maintainer community size.</li>
   <li>
-    <p>At time of writing, GoCD does depend on some libraries/frameworks which require significant effort to upgrade, but are
+    <p>At time of writing <em>(updated: December 2023)</em>, GoCD does depend on some libraries/frameworks which require significant effort to upgrade, but are
 end-of-life, and thus present some level of ongoing risk. If a major vulnerability is discovered in these libraries/frameworks
 that affects GoCD it will either require an urgent upgrade, or forking and patching of those libraries/frameworks. The
 community is not well placed to manage this kind of development. To help you assess risk, at time of writing, they include (but may not be limited to)</p>
@@ -188,7 +188,13 @@ <h3 id="is-it-risky-to-continue-to-use-gocd-from-a-security-standpoint">Is it ri
       <li>Spring Framework 4.3 (EOL December 2020)</li>
       <li>Spring Security 4.2 (EOL October 2020)</li>
       <li>Hibernate ORM 3.6 (EOL February 2012)</li>
-      <li>A small part of the UI relies on <a href="https://angularjs.org/">AngularJS</a> 1 and PrototypeJS 1.6</li>
+      <li>A small part of the UI relies on
+        <ul>
+          <li><a href="https://angularjs.org/">AngularJS</a> 1.0 - plugin view templating support (EOL November 2013)</li>
+          <li><del><a href="https://jquery.com/">jQuery</a> 1.7 - stage and build/job detail views</del> (subsequent upgraded in GoCD 23.4.0)</li>
+          <li><del>PrototypeJS 1.6 - stage and build/job detail views</del> (subsequently replaced with jQuery in GoCD 23.5.0)</li>
+        </ul>
+      </li>
     </ul>
   </li>
 </ul>

2023/02/13/gocd-project-status/index.html

@@ -158,7 +158,7 @@ <h3 id="is-it-risky-to-continue-to-use-gocd-from-a-security-standpoint">Is it ri
   <li>We believe GoCD was built with solid security principles in mind that have generally stood the test of time.</li>
   <li>Software dependencies incorporated within GoCD are <em>generally</em> still under active development, and thus being
 patched/updated. These are being incorporated into new GoCD releases without major issue.</li>
-  <li>GoCD runs on and is built/test using modern, maintained language runtimes (Java 17 LTS, NodeJS 18 LTS, Ruby 3.1)</li>
+  <li>GoCD runs on and is built/test using modern, maintained language runtimes (Java 17 LTS, NodeJS 20 LTS, Ruby 3.1)</li>
   <li>GoCD continues to have good compatibility with latest operating systems, which can be extended to its supported
 <a href="../../../../download.html">Docker images</a>.</li>
 </ul>
@@ -179,7 +179,7 @@ <h3 id="is-it-risky-to-continue-to-use-gocd-from-a-security-standpoint">Is it ri
 Keeping on top of all of these requires non-trivial effort, and is likely not indefinitely sustainable with the current
 contributor/maintainer community size.</li>
   <li>
-    <p>At time of writing, GoCD does depend on some libraries/frameworks which require significant effort to upgrade, but are
+    <p>At time of writing <em>(updated: December 2023)</em>, GoCD does depend on some libraries/frameworks which require significant effort to upgrade, but are
 end-of-life, and thus present some level of ongoing risk. If a major vulnerability is discovered in these libraries/frameworks
 that affects GoCD it will either require an urgent upgrade, or forking and patching of those libraries/frameworks. The
 community is not well placed to manage this kind of development. To help you assess risk, at time of writing, they include (but may not be limited to)</p>
@@ -188,7 +188,13 @@ <h3 id="is-it-risky-to-continue-to-use-gocd-from-a-security-standpoint">Is it ri
       <li>Spring Framework 4.3 (EOL December 2020)</li>
       <li>Spring Security 4.2 (EOL October 2020)</li>
       <li>Hibernate ORM 3.6 (EOL February 2012)</li>
-      <li>A small part of the UI relies on <a href="https://angularjs.org/">AngularJS</a> 1 and PrototypeJS 1.6</li>
+      <li>A small part of the UI relies on
+        <ul>
+          <li><a href="https://angularjs.org/">AngularJS</a> 1.0 - plugin view templating support (EOL November 2013)</li>
+          <li><del><a href="https://jquery.com/">jQuery</a> 1.7 - stage and build/job detail views</del> (subsequent upgraded in GoCD 23.4.0)</li>
+          <li><del>PrototypeJS 1.6 - stage and build/job detail views</del> (subsequently replaced with jQuery in GoCD 23.5.0)</li>
+        </ul>
+      </li>
     </ul>
   </li>
 </ul>

plugins.html

@@ -188,7 +188,7 @@ <h5 class="name"> S3 Artifact Plugin </h5>
                         <a href="https://github.com/Diogomrol/gocd-s3-artifact-plugin">Read more</a>
                       </p>
                       <span class="created-by">by
-                        <a href="https://www.outsystems.com/">OutSystems</a>
+                        <a href="https://github.com/Diogomrol">Diogo Oliveira</a>
                       </span>
                     </div>
                     <div class="actions">

plugins/index.html

@@ -188,7 +188,7 @@ <h5 class="name"> S3 Artifact Plugin </h5>
                         <a href="https://github.com/Diogomrol/gocd-s3-artifact-plugin">Read more</a>
                       </p>
                       <span class="created-by">by
-                        <a href="https://www.outsystems.com/">OutSystems</a>
+                        <a href="https://github.com/Diogomrol">Diogo Oliveira</a>
                       </span>
                     </div>
                     <div class="actions">

releases.html

@@ -68,7 +68,8 @@ <h1 class="caption"><span>What's new?</span></h1>
 
   <div class="v-tabs all-releases">
     <ul class="tabs tab-container-marker release-versions">
-      <li rel="tab-23-4-0" class="tab-marker active">23.4.0 (latest)</li>
+      <li rel="tab-23-5-0" class="tab-marker active">23.5.0 (latest)</li>
+      <li rel="tab-23-4-0" class="tab-marker">23.4.0</li>
       <li rel="tab-23-3-0" class="tab-marker">23.3.0</li>
       <li rel="tab-23-2-0" class="tab-marker">23.2.0</li>
       <li rel="tab-23-1-0" class="tab-marker">23.1.0</li>
@@ -149,7 +150,56 @@ <h1 class="caption"><span>What's new?</span></h1>
     </ul>
 
     <div class="tab_container tab-container-marker">
-      <h3 class="tab-marker tab-accordion_heading d_active" rel="tab-23-4-0">23.4.0 (latest)</h3>
+      <h3 class="tab-marker tab-accordion_heading d_active" rel="tab-23-5-0">23.5.0 (latest)</h3>
+      <div id="tab-23-5-0" class="tab_content" style="display: block;">
+        <div class="content">
+          <p>This release is a maintenance and bug-fix release.</p>
+
+<h4>Enhancements</h4>
+
+<ul>
+  <li><a href="https://github.com/gocd/gocd/issues/12353">#12353</a> - Starting this release, Alpine 3.19 based container images for GoCD Agent are <a href="https://hub.docker.com/r/gocd/gocd-agent-alpine-3.19">available</a>.</li>
+  <li><a href="https://github.com/gocd/gocd/issues/12353">#12353</a> - Build the default GoCD Server image on Alpine 3.19</li>
+  <li><a href="https://github.com/gocd/gocd/issues/12212">#12212</a> - Make template selector dropdowns alphabetically sorted</li>
+</ul>
+
+<h4>Bug fixes</h4>
+
+<ul>
+  <li><a href="https://github.com/gocd/gocd/issues/12220">#12220</a> - Console view toolbar not shown after scrolling on v23.4.0</li>
+  <li><a href="https://github.com/gocd/gocd/issues/12305">#12305</a> - Unable to pick stage from Add Material menu in Chrome on MacOS Sonoma</li>
+  <li><a href="https://github.com/gocd/gocd/issues/12389">#12389</a> - Fix disappearing second+ stages on VSM view after clicking a stage</li>
+  <li><a href="https://github.com/gocd/gocd/issues/12392">#12392</a> - Correct display of "cancelled by" for stage runs other than that being viewed</li>
+</ul>
+
+<h4>Security fixes</h4>
+
+<p>We regularly fix security issues reported by security researchers &amp; upgrade dependencies to mitigate known vulnerabilities.
+Upgrading to the latest release is always recommended.</p>
+
+<p>There are no security fixes specifically known to affect GoCD included in this release.</p>
+
+<h4>APIs</h4>
+
+<p>Improvements, deprecations and breaking changes in the API and plugin API have been moved to their respective changelogs
+- <a href="https://api.gocd.org/23.5.0/#changes-in-23-5-0">API changelog for 23.5.0</a> and
+  <a href="https://plugin-api.gocd.org/23.5.0/#changes-in-gocd-23-5-0">Plugin API changelog for 23.5.0</a>.</p>
+
+<h4>Contributors</h4>
+
+<p>Aravind SV, Chad Wilson, Chris Gillatt, Lewis Jales-Huggins</p>
+
+<h4>Note</h4>
+
+<p>A more comprehensive list of changes for this release can be found <a href="https://github.com/gocd/gocd/issues?q=milestone%3A%22Release+23.5.0%22+is%3Aclosed">here.</a></p>
+
+<p>Found a security issue that needs fixing? Please report it to <a href="https://hackerone.com/gocd">https://hackerone.com/gocd</a></p>
+
+<p>Please report any issues that you observe on <a href="https://github.com/gocd/gocd/issues">GitHub issues</a>.</p>
+
+        </div>
+      </div>
+      <h3 class="tab-marker tab-accordion_heading" rel="tab-23-4-0">23.4.0</h3>
       <div id="tab-23-4-0" class="tab_content" style="display: block;">
         <div class="content">
           <p>This release is mainly a maintenance and bug-fix release.</p>