struts-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From git-site-r...@apache.org
Subject [struts-site] branch asf-site updated: Automatic Site Publish by Buildbot
Date Mon, 28 Dec 2020 08:13:12 GMT
This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/struts-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 8ef3657  Automatic Site Publish by Buildbot
8ef3657 is described below

commit 8ef3657242faf83574792c9d899c4bbbf5ce41a8
Author: buildbot <users@infra.apache.org>
AuthorDate: Mon Dec 28 08:13:09 2020 +0000

    Automatic Site Publish by Buildbot
---
 output/builds.html           | 6 +++---
 output/updating-website.html | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/output/builds.html b/output/builds.html
index 878f5d6..2695f0d 100644
--- a/output/builds.html
+++ b/output/builds.html
@@ -193,7 +193,7 @@ your own applications!)</p>
 <h2 id="nightlybuilds">NightlyBuilds</h2>
 
 <p>As part of our continuous integration practice, we also make available each morning
the
-<a href="https://repository.apache.org/content/repositories/snapshots/org/apache/struts/struts2-assembly/">latest
stable development build.</a></p>
+<a href="https://nightlies.apache.org/x1/dist/struts/">latest stable development build.</a></p>
 
 <p><em>Again: Use at your own risk!</em></p>
 
@@ -206,14 +206,14 @@ the <a href="#SourceCode">source code</a> instead.</p>
 <h2 id="test-builds">Test Builds</h2>
 
 <p>As we prepare for a new release, the project group may create interim <em>test
builds</em>. When test builds are available,
-we post them <a href="http://people.apache.org/builds/struts/">here</a> in binary,
source and library distributions.
+we post them <a href="https://dist.apache.org/repos/dist/dev/struts/">here</a>
in binary, source and library distributions.
 Library distributions include any external dependencies needed to use a product with your
application.</p>
 
 <p>A test build is made available so that it can be reviewed for quality by the Apache
Struts development group.
 When a build is judged “ready for prime time”, it is promoted to “General Availability”
status and may be
 made the “Best Available” release. If the group feels that a build requires more testing,
then it may be marked
 as “Beta” release. When a test build is upgraded to “Beta” or “GA” by a vote
of the project members,
-we make the distribution available as a formal <a href="releases.html">release.</a></p>
+we make the distribution available as a formal <a href="releases.html">release</a>.</p>
 
 <h2 id="maven-snapshots">Maven Snapshots</h2>
 
diff --git a/output/updating-website.html b/output/updating-website.html
index 1e8cf4d..5eb842b 100644
--- a/output/updating-website.html
+++ b/output/updating-website.html
@@ -155,7 +155,7 @@ by a CI server.</p>
 <p>The whole build of the website is orchestrated by <a href="http://s.apache.org/asfyaml">.asf.yaml</a>,
please refer to the docs
 for more details. The main build of the website is performed by <a href="https://ci2.apache.org/#/builders/7">a
buildbot job</a>,
 the staging site is build and deployed by 
-<a href="https://ci-builds.apache.org/job/Struts/job/Struts-staged-site/">a Jenkins
job</a> - buildbot doesn’t support staging site deployment yet.</p>
+<a href="https://builds.apache.org/job/Struts/job/Struts-staged-site/">a Jenkins job</a>
- buildbot doesn’t support staging site deployment yet.</p>
 
 <h2 id="applying-a-change">Applying a change</h2>
 
@@ -166,7 +166,7 @@ please open a Pull Request. The Pull Request will be automatically build
and dep
 
 <h2 id="deploying-javadocs">Deploying JavaDocs</h2>
 
-<p>There is a dedicated <a href="https://ci-builds.apache.org/job/Struts/job/Struts-site-javadocs/">Jenkins
job</a> which is
+<p>There is a dedicated <a href="https://builds.apache.org/job/Struts/job/Struts-site-javadocs/">Jenkins
job</a> which is
 used to update the JavaDocs based on the latest release. If you have a proper privileges
you can start the job
 and provide a Git tag of the latest release, eg. <code class="highlighter-rouge">STRUTS_2_5_22</code>.
Based on the tag, Jenkins will generate a proper
 JavaDocs and deploy them directly into the website. You can verify them by using this <a
href="https://struts.staged.apache.org/maven/struts2-core/apidocs/index.html">link</a>.</p>


Mime
View raw message