aboutsummaryrefslogtreecommitdiffstats
path: root/lib/doorman/pom.xml
blob: 389a05bc182bee6c73f31a7db2c6ee8d107ec320 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <parent>
        <groupId>org.onap.ccsdk.features</groupId>
        <artifactId>ccsdk-features</artifactId>
        <version>1.2.3-SNAPSHOT</version>
        <relativePath>../..</relativePath>
    </parent>

    <groupId>org.onap.ccsdk.features.lib.doorman</groupId>
    <artifactId>doorman</artifactId>

    <name>ccsdk-features :: lib :: ${project.artifactId}</name>
    <description>Doorman - Request prioritization and aggregation queue</description>

    <dependencies>
        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>servlet-api</artifactId>
            <version>2.5</version>
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-api</artifactId>
        </dependency>
        <dependency>
            <groupId>org.onap.ccsdk.features.lib.rlock</groupId>
            <artifactId>rlock</artifactId>
            <version>1.2.3-SNAPSHOT</version>
        </dependency>
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>com.h2database</groupId>
            <artifactId>h2</artifactId>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-simple</artifactId>
            <scope>test</scope>
        </dependency>

    </dependencies>
</project>
gantall <Provide your Jenkins Sandbox username> password= <Refer below steps to get API token> url=https://jenkins.onap.org/sandbox This is deprecated, use job_builder section instead ignore_cache=True ``` ### How to retrieve API token? Login to the [Jenkins Sandbox](https://jenkins.onap.org/sandbox/), go to your user page by clicking on your username. Click **Configure** and then click **Show API Token**. To work on existing jobs or create new jobs, navigate to the `/jjb` directory where you will find all job templates for the project. Follow the below commands to test, update or delete jobs in your sandbox environment. ## To Test a Job: After you modify or create jobs in the above environment, it's good practice to test the job in sandbox environment before you submit this job to production CI environment. `jenkins-jobs --conf jenkins.ini test jjb/ <job-name>` **Example:** `jenkins-jobs --conf jenkins.ini test jjb/ sdc-master-verify-java` If the job you’d like to test is a template with variables in its name, it must be manually expanded before use. For example, the commonly used template `sdc-{stream}-verify-java` might expand to `sdc-master-verify-java`. A successful test will output the XML description of the Jenkins job described by the specified JJB job name. Execute the following command to pipe-out to a directory: `jenkins-jobs --conf jenkins.ini test jjb/ <job-name> -o <directoryname>` The output directory will contain files with the XML configurations. ## To Update a job: Ensure you’ve configured your `jenkins.ini` and verified it by outputting valid XML descriptions of Jenkins jobs. Upon successful verification, execute the following command to update the job to the Jenkins sandbox. `jenkins-jobs --conf jenkins.ini update jjb/ <job-name>` **Example:** `jenkins-jobs --conf jenkins.ini update jjb/ sdc-master-verify-java` ## Trigger jobs from Jenkins Sandbox: Once you push the Jenkins job configuration to the ONAP Sandbox environment, run the job from Jenkins Sandbox webUI. Follow the below process to trigger the build: Step 1: Login into the [Jenkins Sandbox WebUI](https://jenkins.onap.org/sandbox/) Step 2: Click on the **job** which you want to trigger, then click **Build with Parameters**, and finally click **Build**. Step 3: Verify the **Build Executor Status** bar and make sure that the build is triggered on the available executor. In Sandbox you may not see all platforms build executors and you don't find many like in production CI environment. Once the job is triggered, click on the build number to view the job details and the console output. ## To Delete a Job: Execute the following command to Delete a job from Sandbox: `jenkins-jobs --conf jenkins.ini delete jjb/ <job-name>` **Example:** `jenkins-jobs --conf jenkins.ini delete jjb/ sdc-master-verify-java` The above command would delete the `sdc-master-verify-java` job. ## Modify an Existing Job: In the ONAP Jenkins sandbox, you can directly edit or modify the job configuration by selecting the job name and clicking on the **Configure** button. Then, click the **Apply** and **Save** buttons to save the job. However, it is recommended to simply modify the job in your terminal and then follow the previously described steps in **To Test a Job** and **To Update a Job** to perform your modifications. ## More online documentation: https://docs.openstack.org/infra/jenkins-job-builder/