cicd

Las herramientas imprescindibles para desarrolladores Full Stack en 2024

Las herramientas imprescindibles para desarrolladores Full Stack en 2024

Introducción El desarrollo full stack ha avanzado mucho en los últimos años. Para mantenerse competitivo, es crucial contar con herramientas que faciliten el desarrollo, la gestión de proyectos y la colaboración en equipos. En este artículo, compartiré las herramientas que, según mi experiencia, son esenciales para desarrolladores full stack en 2024, abarcando tecnologías de backend, frontend, bases de datos, pruebas y despliegue. 1. Lenguajes y Frameworks Backend Node.js con Express.js Node.js sigue siendo popular para el desarrollo backend gracias a su naturaleza asíncrona y su amplio ecosistema. Express.js es ideal para crear APIs RESTful rápidas y flexibles. NestJS NestJS se…
Read More
Kargo – promote your application changes in a controlled (GitOps) way!

Kargo – promote your application changes in a controlled (GitOps) way!

Simply told, Kargo will bump up your image tag reference in the git whenever new version is released. Not simply told, Kargo is a release management tool with environment as a pipeline delivery solution (few hard to understand phrases and voule'a!) Source: https://akuity.io/blog/why-continuous-promotion/ To continue reading, visit: https://blog.windkube.com/kargo-application/ Source link lol
Read More
Quick fix: com.github.everit-org.json-schema:org.everit.json.schema:jar:1.12.2 was not found

Quick fix: com.github.everit-org.json-schema:org.everit.json.schema:jar:1.12.2 was not found

I've been having this issue in several Mule applications, but all of them happen while I'm trying to use CI/CD pipelines. The full thing I got was this: org.mule.maven.client.api.exception.BundleDependencyNotFoundException: org.eclipse.aether.resolution.ArtifactResolutionException: com.github.everit-org.json-schema:org.everit.json.schema:jar:1.12.2 was not found in https://maven.anypoint.mulesoft.com/api/v3/maven during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of anypoint-exchange-v3 has elapsed or updates are forced Enter fullscreen mode Exit fullscreen mode In summary, this happens because the repositories you are using in your pom.xml don't include this dependency that is needed from MuleSoft for something. This last time I encountered…
Read More
“Streamlined DevOps: Node.js CI/CD Pipeline with GitHub Actions”

“Streamlined DevOps: Node.js CI/CD Pipeline with GitHub Actions”

This project demonstrates a robust Continuous Integration and Continuous Deployment (CI/CD) pipeline setup using GitHub Actions. CI/CD which stands for Continuous Integration and Continuous Delivery/Deployment is a set of practices and tools used in software development to improve the speed and quality of code delivery. Continuous Integration (CI): Developers frequently merge their code changes into a central repository where Automated builds and tests are run.This helps catch and fix integration issues early. Continuous Delivery (CD): This process automatically prepare code changes for release to production by ensuring that the code is always in a deployable state.It automatically deploys every change…
Read More
Cron Job Basics

Cron Job Basics

A cron job is a scheduled task that runs automatically at specified times or intervals on Unix-like operating systems. Cron jobs are used to automate repetitive tasks, like running scripts, backing up databases, or generating reports. Key Components of a Cron Job: Cron Daemon (cron): The cron daemon is a background process that reads scheduled tasks from the crontab file and executes them at the specified times. This process continuously runs on the system and checks every minute for tasks to execute. Crontab: A crontab (cron table) is a simple text file that lists cron jobs, specifying when and what…
Read More
Bridging Jira and GitLab: Automating CI/CD Pipelines for Releases

Bridging Jira and GitLab: Automating CI/CD Pipelines for Releases

Introduction Jira Cloud and GitLab are popular productivity and DevOps platforms widely used by many organizations and software development teams. While the integration between these platforms has significantly improved in recent years, there are still areas in common software development tasks that require manual effort or custom integration solutions. One such area is software releases. In this post, I will demonstrate how to streamline and automate this process, it will be useful for teams who: Plan and manage tasks in Jira; Use Jira versions for planning product milestones and releases; Keep their source code in GitLab; Use GitLab's CI/CD pipelines…
Read More
Scheduled Test Workflow Documentation

Scheduled Test Workflow Documentation

Overview This documentation provides a detailed explanation of the setup for a cron job scheduled test in a GitHub Actions workflow. The purpose of this setup is to automate the execution of test scripts against a Postman collection every 15 minutes, ensuring continuous testing and monitoring of the boilerplate repository's API endpoints. GitHub Actions Workflow Configuration name: Scheduled Test on: schedule: - cron: '*/15 * * * *' jobs: build: runs-on: ubuntu-latest steps: - name: Checkout repository uses: actions/checkout@v3 - name: Run test script env: POSTMAN_API_KEY: ${{ secrets.POSTMAN_API_KEY }} API_URL: ${{ secrets.API_URL }} run: | cd qa chmod +x test.sh…
Read More
Creating Envless Angular-application

Creating Envless Angular-application

Ways to move from hard-coded code for each environment to a universal build that can be used anywhere Introduction As you all know, Angular has its own tools for building an application for different environments Configuring application environments This is accomplished by creating and using the environment.<env>.ts file for the appropriate environment in the build. These allow you to switch between settings for: Development (environment.ts) Testing (environment.test.ts) Production (environment.prod.ts) The main tasks of environment.ts files are: API settings. Each file can contain different URLs for API servers depending on the environment. Optimization. The production file disables debugging features and enables…
Read More
Running Jobs in a Container via GitHub Actions Securely

Running Jobs in a Container via GitHub Actions Securely

Like any modern CI/CD platform, GitHub allows users to run CI jobs in a container. This is great for running consistent and reproducible CI jobs as well as reducing the amount of setup steps that is required for the job to run (e.g., running actions/setup-python to install Python environment and installing necessary packages via pip) as those environments and dependencies can be baked into the container. In order to make use of this feature, in the GitHub yaml file, specify the container to run any steps in a job via jobs.<job_id>.container. This will tell GitHub to spin up a container…
Read More
DevOps Meets Cybersecurity -> DevSecOps

DevOps Meets Cybersecurity -> DevSecOps

In the field of software development and IT operations, two methodologies have emerged as pivotal players: DevOps and DevSecOps. While they share common roots, their approaches and focuses differ significantly. As organizations strive to balance speed, efficiency, and security in their development processes, understanding the nuances between these two practices becomes crucial. The Coexistence of DevOps and DevSecOpsThe digital age has ushered in an era where software development and deployment need to be faster, more efficient, and increasingly secure. DevOps emerged as a revolutionary approach, breaking down silos between development and operations teams. However, as cyber threats became more sophisticated,…
Read More
No widgets found. Go to Widget page and add the widget in Offcanvas Sidebar Widget Area.