npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@white67/dummy-node-project

v2025.4.24-195055

Published

A simple to do server

Readme

Sprawozdanie

Lab 5. Pipeline, Jenkins, izolacja etapów

1. Utworzenie instancji Jenkinsa

Instancja Jenkins została już utworzona na poprzednich zajęciach.

docker network create jenkins

Jenkins already exists

Zapoznanie się z instrukcją instalacji Jenkinsa i uruchomienie obrazu kontenera Dockera, który eksponuje środowisko zagnieżdżone:

docker run   --name jenkins-docker   --rm   --detach   --privileged   --network jenkins   --network-alias docker   --env DOCKER_TLS_CERTDIR=/certs   --volume jenkins-docker-certs:/certs/client   --volume jenkins-data:/var/jenkins_home   --publish 2376:2376   docker:dind

Docker run DIND

Przygotowanie obrazu blueocean na podstawie obrazu Jenkinsa:

docker build -t myjenkins-blueocean:2.492.3-1 .

Przygotowanie obrazu blueocean

Uruchomienie kontenera Jenkinsa

docker run --name jenkins-blueocean --restart=on-failure --detach   --network jenkins --env DOCKER_HOST=tcp://docker:2376   --env DOCKER_CERT_PATH=/certs/client --env DOCKER_TLS_VERIFY=1   --publish 8080:8080 --publish 50000:50000   --volume jenkins-data:/var/jenkins_home   --volume jenkins-docker-certs:/certs/client:ro   myjenkins-blueocean:2.492.3-1

Docker run jenkins-blueocean

Wykonanie przekierowania portu na 8080 tak aby możliwe było połączenie się z Jenkinsem pod adresem localhost:8080:

Port forwarding

2. Uruchomienie prostego projektu

Po poprawnym skonfigorowaniu Jenkinsa (wstępna instalacja wtyczek) utworzono pierwszy projekt, który ma na celu wyświetlenie uname oraz pobranie obrazu kontenera ubuntu:

uname -a
docker pull ubuntu

Weryfikacja logów prostego projektu

Weryfikacja statusu projektu

3. Uruchomienie projektu typu pipeline

uname -a
docker pull ubuntu

Treść pipeline:

pipeline {
    agent any

    stages {
        stage('Klonowanie repozytorium') {
            steps {
                script {
                    sh '''
                    if [ -d "MDO2025_INO" ]; then
                        rm -rf MDO2025_INO
                    fi
                    git clone https://github.com/InzynieriaOprogramowaniaAGH/MDO2025_INO
                    '''
                    dir('MDO2025_INO') {
                        sh 'git checkout KP415903'
                    }
                }
            }
        }
        
        stage('Build "build image"') {
            steps {
                script {
                    dir('MDO2025_INO/ITE/GCL06/KP415903/Sprawozdanie1/Lab3 dockerfiles/') {
                        sh 'pwd'
                        sh 'ls -la'
                        sh 'docker build -t nodebuild -f Dockerfile.nodebuild .'
                    }
                }
            }
        }
        
        stage('Build "test image"') {
            steps {
                script {
                    dir('MDO2025_INO/ITE/GCL06/KP415903/Sprawozdanie1/Lab3 dockerfiles/') {
                        sh 'docker build -t nodetest -f Dockerfile.nodetest .'
                        sh 'docker images'
                    }
                }
            }
        }
    }
}

Zweryfikowanie logów, czeli poprawności wykonania skryptu pipeline.

Pipeline script logs Pipeline script logs Pipeline script logs Pipeline script logs

Pipeline status: success