Skip to content

Commit

Permalink
Merge pull request #321 from arvindsv/upgrade-hugo
Browse files Browse the repository at this point in the history 
Upgrade Hugo to 0.55.6
  • Loading branch information
@arvindsv
arvindsv authored Jun 17, 2019
2 parents 1d76c1a + 163dfd7 commit f398b57
Show file tree
Hide file tree
Showing 16 changed files with 387 additions and 317 deletions.
61 changes: 33 additions & 28 deletions content/advanced_usage/admin_install_multiple_agents.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -26,9 +26,10 @@ Just after the line \#include ../conf/wrapper-license.conf, add
- set.GO\_AGENT\_DIR=C:\\Program Files\\Go Agent 2
- set.GO\_AGENT\_JAVA\_HOME=%GO\_AGENT\_DIR%\\jre
- Run the following command
```bash

{{< highlight bash >}}
sc create GoAgent2 binPath= "\"C:\Program Files\Go Agent 2\cruisewrapper.exe\" -s \"C:\Program Files\Go Agent 2\config\wrapper-agent.conf\""
```
{{< / highlight >}}

- Start "GoAgent2" service

Expand All @@ -45,9 +46,9 @@ sc create GoAgent2 binPath= "\"C:\Program Files\Go Agent 2\cruisewrapper.exe\" -
- Assuming your first agent in at /Applications/Go Agent.app, copy that to another location, say
/Applications/Go Agent 2.app. Once you do that, you can start the application like this:

```bash
{{< highlight bash >}}
GO_APPLICATION_NAME="Go Agent 2" open /Applications/Go\ Agent\ 2.app
```
{{< / highlight >}}

The logs and other files related to the second agent should be available at
"<user-home>/Library/Application Support/Go Agent 2" and the icon in the dock
Expand All @@ -62,30 +63,34 @@ sc create GoAgent2 binPath= "\"C:\Program Files\Go Agent 2\cruisewrapper.exe\" -

- [Install your first agent with the installer](../installation/installing_go_agent.html)
- To create a second agent on the same host, run this as root:
```bash
cp /etc/init.d/go-agent /etc/init.d/go-agent-1
sed -i 's/# Provides: go-agent$/# Provides: go-agent-1/g' /etc/init.d/go-agent-1
ln -s /usr/share/go-agent /usr/share/go-agent-1
cp -p /etc/default/go-agent /etc/default/go-agent-1
mkdir /var/{lib,log}/go-agent-1
chown go:go /var/{lib,log}/go-agent-1
```

{{< highlight bash >}}
cp /etc/init.d/go-agent /etc/init.d/go-agent-1
sed -i 's/# Provides: go-agent$/# Provides: go-agent-1/g' /etc/init.d/go-agent-1
ln -s /usr/share/go-agent /usr/share/go-agent-1
cp -p /etc/default/go-agent /etc/default/go-agent-1
mkdir /var/{lib,log}/go-agent-1
chown go:go /var/{lib,log}/go-agent-1
{{< / highlight >}}

- To enable starting the go-agent service during system boot:
- on Debian:
```bash
insserv go-agent-1
```

- on Ubuntu:
```bash
update-rc.d go-agent-1 defaults
```
- on Debian:

{{< highlight bash >}}
insserv go-agent-1
{{< / highlight >}}

- on Centos and Redhat:
```bash
chkconfig go-agent-1 on
```
- on Ubuntu:

{{< highlight bash >}}
update-rc.d go-agent-1 defaults
{{< / highlight >}}

- on Centos and Redhat:

{{< highlight bash >}}
chkconfig go-agent-1 on
{{< / highlight >}}

- You can now start or stop the second agent using /etc/init.d/go-agent-1
(passing it the start or stop) arguments as usual. Logs will be written to
Expand All @@ -100,6 +105,6 @@ sc create GoAgent2 binPath= "\"C:\Program Files\Go Agent 2\cruisewrapper.exe\" -
- Make an empty folder called /var/lib/go-agent-2
- In this folder, run

```bash
java -jar /usr/share/go-agent/agent-bootstrapper.jar -serverUrl https://127.0.0.1/go &
```
{{< highlight bash >}}
java -jar /usr/share/go-agent/agent-bootstrapper.jar -serverUrl https://127.0.0.1/go &
{{< / highlight >}}
226 changes: 113 additions & 113 deletions content/configuration/configuration_reference.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2413,21 +2413,21 @@ All paths specified are relative to the pipeline working directory.

**Examples**

- Invoke Ant, specifying a set of targets to run:
- Invoke Ant, specifying a set of targets to run:

```xml
<tasks>
<ant target="-Drun=all clean.ivy.localivy clean ft.long_running"/>
</tasks>
```
{{< highlight xml >}}
<tasks>
<ant target="-Drun=all clean.ivy.localivy clean ft.long_running"/>
</tasks>
{{< / highlight >}}

- Invoke Ant in a specific working directory with a set of targets:

```xml
<tasks>
<ant workingdir="build" buildfile="mybuild.xml" target="-Drun=all clean.ivy.localivy clean ft.long_running"/>
</tasks>
```
{{< highlight xml >}}
<tasks>
<ant workingdir="build" buildfile="mybuild.xml" target="-Drun=all clean.ivy.localivy clean ft.long_running"/>
</tasks>
{{< / highlight >}}

[top](#top)

Expand All @@ -2447,13 +2447,13 @@ All paths specified are relative to the pipeline working directory.

**Examples**

- Invoke ruby, specifying the working directory as **tools/my-ruby-tool** and executing the ruby script **backup.rb**.
- Invoke ruby, specifying the working directory as **tools/my-ruby-tool** and executing the ruby script **backup.rb**.

```xml
<tasks>
<exec command="/usr/local/bin/ruby" args="backup.rb" workingdir="tools/my-ruby-tool"/>
</tasks>
```
{{< highlight xml >}}
<tasks>
<exec command="/usr/local/bin/ruby" args="backup.rb" workingdir="tools/my-ruby-tool"/>
</tasks>
{{< / highlight >}}

[top](#top)

Expand All @@ -2470,25 +2470,25 @@ On Windows you should specify the full name of your script file such as "mybuild

**Examples**

- Echo something on Windows:
- Echo something on Windows:

```xml
<exec command="cmd">
<arg>/c</arg>
<arg>echo</arg>
<arg>something to print out</arg>
</exec>
```
{{< highlight xml >}}
<exec command="cmd">
<arg>/c</arg>
<arg>echo</arg>
<arg>something to print out</arg>
</exec>
{{< / highlight >}}

- Run command with pipe character in arguments:
- Run command with pipe character in arguments:

```xml
<exec command="MsBuild">
<arg>D:\projects\project\project-8.sln</arg>
<arg>/REBUILD</arg>
<arg>/CFG="Release_99|Win32"</arg>
</exec>
```
{{< highlight xml >}}
<exec command="MsBuild">
<arg>D:\projects\project\project-8.sln</arg>
<arg>/REBUILD</arg>
<arg>/CFG="Release_99|Win32"</arg>
</exec>
{{< / highlight >}}

[top](#top)

Expand Down Expand Up @@ -2576,89 +2576,89 @@ Go will not fetch the artifact again if it has not changed. The directory path i

**Example:**

1. Fetch all artifacts in the directory 'pkg' from the previous stage in the same pipeline and put them under the directory 'lib'
1. Fetch all artifacts in the directory 'pkg' from the previous stage in the same pipeline and put them under the directory 'lib'

```xml
<pipelines>
<pipeline name="go">
...
<stage name="dev">
<jobs>
<job name="unit">
<artifacts>
<artifact type="build" src="target/deployable.jar" dest="pkg"/>
<artifact type="external" id="artifact_jar" storeId="dummy-s3">
<configuration>
<property>
<key>Filename</key>
<value>target/deployable.jar</value>
</property>
</configuration>
</artifact>
</artifacts>
</job>
</jobs>
</stage>
<stage name="ft">
<jobs>
<job name="functional">
<tasks>
<fetchartifact artifactOrigin="gocd" stage="dev" job="unit" srcdir="pkg" dest="lib"/>
<fetchartifact artifactOrigin="external" stage="dev" job="unit" artifactId="artifact_jar">
<configuration>
<property>
<key>dest_on_agent</key>
<value>release_candidate.jar</value>
</property>
</configuration>
</fetchartifact>
</tasks>
</job>
</jobs>
</stage>
</pipeline>
</pipelines>
```

2. Fetch a single artifact from a stage in the upstream pipeline 'framework' and put it under the directory 'lib'

```xml
<pipeline name="go">
<materials>
<pipeline name="framework" stage="ft"/>
</materials>
<stage name="dev">
<jobs>
<job name="unit">
<tasks>
<fetchartifact origin="gocd" pipeline="framework" stage="dev" job="unit"
srcfile="pkg/deployable.jar" dest="lib" />
</tasks>
</job>
</jobs>
</stage>
</pipeline>
```
{{< highlight xml >}}
<pipelines>
<pipeline name="go">
...
<stage name="dev">
<jobs>
<job name="unit">
<artifacts>
<artifact type="build" src="target/deployable.jar" dest="pkg"/>
<artifact type="external" id="artifact_jar" storeId="dummy-s3">
<configuration>
<property>
<key>Filename</key>
<value>target/deployable.jar</value>
</property>
</configuration>
</artifact>
</artifacts>
</job>
</jobs>
</stage>
<stage name="ft">
<jobs>
<job name="functional">
<tasks>
<fetchartifact artifactOrigin="gocd" stage="dev" job="unit" srcdir="pkg" dest="lib"/>
<fetchartifact artifactOrigin="external" stage="dev" job="unit" artifactId="artifact_jar">
<configuration>
<property>
<key>dest_on_agent</key>
<value>release_candidate.jar</value>
</property>
</configuration>
</fetchartifact>
</tasks>
</job>
</jobs>
</stage>
</pipeline>
</pipelines>
{{< / highlight >}}

3. Fetch a single artifact from a stage in an ancestor pipeline 'Build' and put it under the directory 'pkg'
2. Fetch a single artifact from a stage in the upstream pipeline 'framework' and put it under the directory 'lib'

```xml
<pipeline name="deploy">
<materials>
<pipeline name="acceptance" stage="ft"/>
</materials>
<stage name="deply-pkg">
<jobs>
<job name="deploy-win">
<tasks>
<fetchartifact origin="gocd" pipeline="build" stage="dist" job="create-installer"
srcfile="installers/deployable-setup.exe" dest="installer" />
</tasks>
</job>
</jobs>
</stage>
</pipeline>
```
{{< highlight xml >}}
<pipeline name="go">
<materials>
<pipeline name="framework" stage="ft"/>
</materials>
<stage name="dev">
<jobs>
<job name="unit">
<tasks>
<fetchartifact origin="gocd" pipeline="framework" stage="dev" job="unit"
srcfile="pkg/deployable.jar" dest="lib" />
</tasks>
</job>
</jobs>
</stage>
</pipeline>
{{< / highlight >}}

3. Fetch a single artifact from a stage in an ancestor pipeline 'Build' and put it under the directory 'pkg'

{{< highlight xml >}}
<pipeline name="deploy">
<materials>
<pipeline name="acceptance" stage="ft"/>
</materials>
<stage name="deply-pkg">
<jobs>
<job name="deploy-win">
<tasks>
<fetchartifact origin="gocd" pipeline="build" stage="dist" job="create-installer"
srcfile="installers/deployable-setup.exe" dest="installer" />
</tasks>
</job>
</jobs>
</stage>
</pipeline>
{{< / highlight >}}

[top](#top)

Expand Down
20 changes: 10 additions & 10 deletions content/faq/admin_out_of_disk_space.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -70,22 +70,22 @@ Now, if you add this to a system [crontab](http://en.wikipedia.org/wiki/Cron), y

If compressing large artifacts is not giving you enough free space, another thing you can do is attach a larger disk drive to store artifacts. After the drive is attached to the system, we can easily change the location GoCD uses for it's artifact repository.

- Find the location of the GoCD configuration file
- Navigate to the [Admin](../navigation/administration_page.html) section
- Find the location of the GoCD configuration file
- Navigate to the [Admin](../navigation/administration_page.html) section
![](../images/topnav_admin.png)
- Click on the "Config XML" tab
- The location of the configuration file is listed here
- Click on the "Config XML" tab
- The location of the configuration file is listed here
![](../images/4_find_config_location.png)
- Install the new drive
- Shut down GoCD server
- Copy all files from the original artifact repository location to the new drive
- Change the artifact repository location in the configuration file
```xml
- Install the new drive
- Shut down GoCD server
- Copy all files from the original artifact repository location to the new drive
- Change the artifact repository location in the configuration file
```
<server artifactsDir="/path/to/new/artifacts">
...
</server>
```
- Start up GoCD server and verify you still have access to old artifacts
- Start up GoCD server and verify you still have access to old artifacts

## Delete unused artifacts

Expand Down
Loading

0 comments on commit f398b57

Please sign in to comment.