Skip to content

Commit 0c936aa

Browse files
authored
Merge pull request #20 from CDOT-CV/fix/ci-updates
CI Updates
2 parents f86a47b + 01c4600 commit 0c936aa

File tree

3 files changed

+58
-13
lines changed

3 files changed

+58
-13
lines changed

.azure/README.md

+47
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
# Azure Pipeline Configuration
2+
3+
This directory contains the Azure DevOps pipeline configuration for the JPO UTILS project.
4+
5+
## Overview
6+
7+
The pipeline configuration in `azure-pipelines.yml` is primarily used for Continuous Integration (CI) in the CDOT-CV fork of the JPO UTILS project. It serves as the first step in a two-stage process:
8+
9+
1. **Build Pipeline (this configuration)**
10+
- Triggers on changes to the `develop` branch
11+
- Monitors specific project directories for changes:
12+
- `jikkou/*`
13+
- `kafka-connect/*`
14+
- Copies all source files to the artifact staging directory
15+
- Publishes the source code as an artifact named 'jpo-utils-services'
16+
17+
2. **Release Pipeline (configured in Azure DevOps)**
18+
- Uses the published artifact from the build pipeline
19+
- Handles Docker image building and deployment
20+
- Configuration is managed through the Azure DevOps web interface
21+
22+
## Pipeline Trigger
23+
24+
The pipeline automatically triggers when:
25+
26+
- Changes are pushed to the `develop` branch
27+
- Changes occur in any of the monitored project directories
28+
29+
## Pipeline Steps
30+
31+
1. **Copy Files**
32+
- Copies project files to the artifact staging directory
33+
- Excludes certain files/directories by default:
34+
- `data` directories
35+
- `docs` directories
36+
- Markdown (`.md`) files
37+
- `.github` directories
38+
- `monitoring` directories
39+
- `mongo` directories
40+
41+
2. **Publish Artifact**
42+
- Creates an artifact named 'jpo-utils-services'
43+
- Makes the source code available for the release pipeline
44+
45+
## Note
46+
47+
The actual Docker build process and deployment steps are configured in the Azure DevOps release pipeline, which is separate from this build pipeline configuration. The release pipeline picks up the artifact produced by this build pipeline and performs the necessary build and deployment steps.

azure-pipelines.yml .azure/azure-pipelines.yml

+11-6
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
1-
# Starter pipeline
2-
# Start with a minimal pipeline that you can customize to build and deploy your code.
3-
# Add steps that build, run tests, deploy, and more:
4-
# https://aka.ms/yaml
1+
# Azure pipeline used to trigger builds of the JPO UTILS project
2+
# This pipeline is primarily used for CI in the CDOT-CV fork
53

64
trigger:
75
branches:
@@ -18,8 +16,15 @@ pool:
1816
steps:
1917
- task: CopyFiles@2
2018
inputs:
21-
SourceFolder: '.'
22-
Contents: '**'
19+
SourceFolder: '$(Build.SourcesDirectory)'
20+
Contents: |
21+
**
22+
!**/data/**
23+
!**/docs/**
24+
!**/*.md
25+
!**/.github
26+
!**/monitoring/**
27+
!**/mongo/**
2328
TargetFolder: '$(Build.ArtifactStagingDirectory)'
2429

2530
# Publish the artifacts directory for consumption in publish pipeline

docker-compose-kafka.yml

-7
Original file line numberDiff line numberDiff line change
@@ -76,13 +76,6 @@ services:
7676
KAFKA_TOPIC_MIN_INSYNC_REPLICAS: ${KAFKA_TOPIC_MIN_INSYNC_REPLICAS:-1}
7777
KAFKA_TOPIC_RETENTION_MS: ${KAFKA_TOPIC_RETENTION_MS:-300000}
7878
KAFKA_TOPIC_DELETE_RETENTION_MS: ${KAFKA_TOPIC_DELETE_RETENTION_MS:-3600000}
79-
80-
KAFKA_TOPIC_CREATE_ODE: ${KAFKA_TOPIC_CREATE_ODE:-true}
81-
KAFKA_TOPIC_CREATE_GEOJSONCONVERTER: ${KAFKA_TOPIC_CREATE_GEOJSONCONVERTER:-true}
82-
KAFKA_TOPIC_CREATE_CONFLICTMONITOR: ${KAFKA_TOPIC_CREATE_CONFLICTMONITOR:-true}
83-
KAFKA_TOPIC_CREATE_DEDUPLICATOR: ${KAFKA_TOPIC_CREATE_DEDUPLICATOR:-false}
84-
KAFKA_TOPIC_CREATE_MECDEPOSIT: ${KAFKA_TOPIC_CREATE_MECDEPOSIT:-false}
85-
KAFKA_TOPIC_CREATE_OTHER: ${KAFKA_TOPIC_CREATE_OTHER:-false}
8679

8780
KAFKA_SECURITY_PROTOCOL: ${KAFKA_SECURITY_PROTOCOL:-PLAINTEXT}
8881
KAFKA_SASL_MECHANISM: ${KAFKA_SASL_MECHANISM}

0 commit comments

Comments
 (0)