Skip to content
This repository was archived by the owner on Nov 17, 2020. It is now read-only.

Commit eb06bdb

Browse files
author
Libor Krzyzanek
committed
Added Openshift default preferences
1 parent 13f7ed0 commit eb06bdb

22 files changed

+730
-0
lines changed

.openshift/action_hooks/build

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
#!/bin/bash
2+
# This is a simple build script and will be executed on your CI system if
3+
# available. Otherwise it will execute while your application is stopped
4+
# before the deploy step. This script gets executed directly, so it
5+
# could be python, php, ruby, etc.

.openshift/action_hooks/deploy

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
#!/bin/bash
2+
# This deploy hook gets executed after dependencies are resolved and the
3+
# build hook has been run but before the application has been started back
4+
# up again. This script gets executed directly, so it could be python, php,
5+
# ruby, etc.

.openshift/action_hooks/post_deploy

+4
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
#!/bin/bash
2+
# This is a simple post deploy hook executed after your application
3+
# is deployed and started. This script gets executed directly, so
4+
# it could be python, php, ruby, etc.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
#!/bin/bash
2+
3+
# The pre_start_cartridge and pre_stop_cartridge hooks are *SOURCED*
4+
# immediately before (re)starting or stopping the specified cartridge.
5+
# They are able to make any desired environment variable changes as
6+
# well as other adjustments to the application environment.
7+
8+
# The post_start_cartridge and post_stop_cartridge hooks are executed
9+
# immediately after (re)starting or stopping the specified cartridge.
10+
11+
# Exercise caution when adding commands to these hooks. They can
12+
# prevent your application from stopping cleanly or starting at all.
13+
# Application start and stop is subject to different timeouts
14+
# throughout the system.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
#!/bin/bash
2+
3+
# The pre_start_cartridge and pre_stop_cartridge hooks are *SOURCED*
4+
# immediately before (re)starting or stopping the specified cartridge.
5+
# They are able to make any desired environment variable changes as
6+
# well as other adjustments to the application environment.
7+
8+
# The post_start_cartridge and post_stop_cartridge hooks are executed
9+
# immediately after (re)starting or stopping the specified cartridge.
10+
11+
# Exercise caution when adding commands to these hooks. They can
12+
# prevent your application from stopping cleanly or starting at all.
13+
# Application start and stop is subject to different timeouts
14+
# throughout the system.

.openshift/action_hooks/pre_build

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
#!/bin/bash
2+
# This is a simple script and will be executed on your CI system if
3+
# available. Otherwise it will execute while your application is stopped
4+
# before the build step. This script gets executed directly, so it
5+
# could be python, php, ruby, etc.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
#!/bin/bash
2+
# This is a simple bash script and will be sourced prior to building
3+
# your application. This script can be used to modify the Maven build
4+
# arguments for non-CI/Jenkins builds by exporting MAVEN_ARGS. The default
5+
# is "clean package -Popenshift -DskipTests"
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
#!/bin/bash
2+
3+
# The pre_start_cartridge and pre_stop_cartridge hooks are *SOURCED*
4+
# immediately before (re)starting or stopping the specified cartridge.
5+
# They are able to make any desired environment variable changes as
6+
# well as other adjustments to the application environment.
7+
8+
# The post_start_cartridge and post_stop_cartridge hooks are executed
9+
# immediately after (re)starting or stopping the specified cartridge.
10+
11+
# Exercise caution when adding commands to these hooks. They can
12+
# prevent your application from stopping cleanly or starting at all.
13+
# Application start and stop is subject to different timeouts
14+
# throughout the system.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
#!/bin/bash
2+
3+
# The pre_start_cartridge and pre_stop_cartridge hooks are *SOURCED*
4+
# immediately before (re)starting or stopping the specified cartridge.
5+
# They are able to make any desired environment variable changes as
6+
# well as other adjustments to the application environment.
7+
8+
# The post_start_cartridge and post_stop_cartridge hooks are executed
9+
# immediately after (re)starting or stopping the specified cartridge.
10+
11+
# Exercise caution when adding commands to these hooks. They can
12+
# prevent your application from stopping cleanly or starting at all.
13+
# Application start and stop is subject to different timeouts
14+
# throughout the system.

.openshift/config/modules/README

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
Place your JBoss EAP6.0 modules in this directory. This directory is added to the
2+
module path of the EAP6.0 server associated with your application. It has the
3+
same structure as the standard EAP6.0 modules directory.
4+
5+
The modules placed in this directory will be added to or override the default modules
6+
provided by the OpenShift JBoss EAP6.0 cartridge.
7+
8+
Scenarios:
9+
1) Replace a default module with a new module that contains a bug fix or new feature
10+
2) Add a module that does not exist in the base OpenShift EAP6.0 cartridge in order to add
11+
a new component. Typically these new modules will need to be enabled and configured in
12+
standalone.xml
13+
14+
Unless one of the above scenarios is required there is no need to modify the
15+
modules directory.
16+
17+
NOTE: Replacing default modules as in scenario 1 can cause conflicts between modules so
18+
should be done with caution and adequate testing.

0 commit comments

Comments
 (0)