Goal: Migrate Jenkins to GitHub Actions while minimizing downtime, and maintaining CI/CD continuity.
Objectives: Understand current state, identify gaps, and define migration scope.
| #!/usr/bin/env bash | |
| set -ex | |
| error_files=$(rg 'migration failed' | cut -d':' -f1 | sort | uniq) | |
| echo "Failure,Assignee,Status,Reason,Notes" | |
| for file in $error_files; do | |
| repo="$(grep 'GITHUB REPO' $file | perl -pe 's/.*GITHUB REPO: (.*)/\1/')" | |
| error="$(grep 'ERROR' $file | tail -1 | perl -pe 's/.*\[ERROR\] (.*)/\1/'| perl -pe 's/"/""/g')" | |
| echo "\"${repo}.log\",,,,\"${error}\"" |
| 1. JobNimbus | |
| • Pros: Highly customizable, robust features for project management, and integration with tools like SumoQuote. Great for team communication and pipeline tracking. | |
| • Cons: Steep learning curve, occasional issues with integrations and automations, and challenges with larger jobs. | |
| • Best For: Larger teams needing extensive customization and integrations. | |
| • Rating: Generally well-reviewed as a solid all-around CRM. | |
| 2. iRoofing | |
| • Pros: Excellent for roof measurements, quoting, and visualization tools. Allows contractors to measure roofs directly from an iPad. | |
| • Cons: Limited CRM features (more focused on quoting), not cloud-based (data is stored locally), and lacks robust communication or pipeline management tools. | |
| • Best For: Contractors focused on estimating and quoting rather than full CRM functionality. | |
| • Rating: Mixed reviews due to its limited scope but praised for its measurement tools. |
| Category | ISPW | UrbanCode | GAP |
|---|---|---|---|
| Mainframe Environment Integration | - Native integration with z/OS and mainframe tools. - Strong support for COBOL, PL/I, CICS, DB2. - Tailored workflows for mainframe. | - Integrates with mainframe systems via plugins. - Requires additional setup for mainframe-specific tasks. | ISPW offers deeper and more seamless integration with mainfr |
| #!/usr/bin/env python3 | |
| import json | |
| import requests | |
| from bs4 import BeautifulSoup | |
| quotes = [] | |
| for i in range(1, 101): | |
| url = f'https://www.goodreads.com/quotes?page={i}' | |
| headers = { | |
| 'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36' |
| Feature | CA Endevor | IBM DBB | Gap Analysis |
|---|---|---|---|
| Version Control | Integrated, proprietary version control | External version control (e.g., Git) | Migration to an external VCS may be required. |
| Branching and Merging | Limited branching capabilities | Full branching and merging via Git | Improved with Git, may need developer training. |
| Code History | Proprietary history tracking | Git provides detailed commit history | Migration of historical data may be complex. |
Deployment protection rules are used to enforce checks and policies specifically around the deployment of code to environments. You would use a deployment protection rule when you want to ensure that certain conditions are met before code can be deployed. This can include:
[toc]
Traffic situations can change fast, especially around intersections and in curves. The Basic Street Strategies in this section will help you:
| $ TEST_1=one | |
| $ TEST_2=two | |
| $ PATTERN2_1=one | |
| $ PATTERN2_2=two | |
| $ docker run -d --name test $(for var in $(set | grep -E '^TEST_|^PATTERN2_'); do printf -- '-e "%s" ' $var; done) nginx | |
| 541a23d4e432b375f71b081593d533de0aeb0b918f74d911bee7c36c95bcc4e3 | |
| $ docker ps | |
| CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES |