#CI
[Перевод] Как запустить контейнер Docker внутри конвейера GitLab CI
Довольно часто мы используем GitLab CI для докеризации наших приложений. Но как запустить контейнер Docker из GitLab Container Registry? Можно ли использовать Docker Compose? Делимся переводом статьи, в которой автор отвечает на эти вопросы и рассказывает о функции services keyword в GitLab CI, которая позволяет запустить один или несколько образов Docker и связать их с вашим заданием.
El Coeficiente Intelectual (CI) ha sido un faro en la evaluación de la inteligencia durante décadas, pero ¿qué tan completo es este indicador?
Today is my last day at the tech co-op @igalia !
During my ~2 years there, I got to work on fun stuff like a #mesa3d CI for RADV (called #ci-tron, by @mupuf ), and I helped do some neat stuff in the #SteamDeck's #SteamOS.
Lots of great folks at Igalia working on some great #FOSS, I'll definitely miss being at that place!
A. La barre : interactions médicamenteuses contre-indiquées en #MG (#Primege Normandie)
Alertes d'interaction en excès (alerte fatigue)
Pas de prise en compte du contexte (patient, dose)
4 niveaux de contrainte (prendre en compte -> #CI absolue)
200 000 hospitalisations et 2000 décès (iatrostat)
Prévalence et top 20 des associations contre-indiquées
Étude rétrospective observationnelles
#CNGE2023
Interested in hearing people's experiences with #CI merge queues of different kinds! If you've used, or have driven a switch to:
* any version of #bors,
* #GitHub merge queues, or
* something else
I'd love to hear your thoughts!
Particularly:
* How many developers work on the repo?
* What's your favorite thing about whichever one you use?
* What's your least favorite thing about it?
Reply to this, DM me, or email me at rain at sunshowers.io :)
Please boost for reach!
Lots of folks liked my self-hosted #Linktree clone built with #Hugo and the Lynx theme earlier this week!
Quite a few people got in touch asking if I could walk them through how to go from initializing a new project to getting it deployed and visible on the internet
So here it is! From Zero to your very own Linktree-style website deployed on #Cloudflare Pages 🚀
And it will automatically update whenever you push new changes with a fancy #CI setup!
saving 100+ minutes of CI compute time on each single CI workflow by replacing {rmarkdown} with {markdown} for vignette engine via {knitr}. #rstats #ci thanks @yihui ! https://github.com/Rdatatable/data.table/pull/5773
A question for all #CI and #Docker people. What is your preferred way to deploy docker containers on a standalone #linux host via a CI task. Do you use ssh and run commands on the target host? Or do you use a ssh tunnel to connect to the daemon? Or do you even expose the docker daemon and directly connect to it? Or is there a better way?
Cool, the more we are working on the Qualcomm platforms, the better! You can join us on IRC at #ci-tron on OFTC.
As for how to getting a full rootfs booting without stressing the storage too much: we created boot2container, an initrd to boot containers. This means the layers are cached and not re-downloaded every time. It also supports network filesystems if needed :)
You may want to have a chat with @craftyguy who also works on @postmarketOS and who has been working on CI-tron!
Prompted by @filiph I redid my release automation and accidentally stumbled upon a great feature of the #GitHub #actions #CI: manual triggers.
These can have rudimentary UI elements - here I'm using checkboxes to select which platform to build my #Flutter app for.
The version is generated by reading from pubspec.yaml and appending the CI build number as patch.
The only thing that's missing now is a way to reset the patch number when the major or minor changes.
https://github.com/cachapa/tudo/blob/master/.github/workflows/release.yml
Автоматическая генерация CI/CD пайплайна для развёртывания инфраструктуры
При нашей работе мы используем подход «Инфраструктура как код». Однако в процессе его использования мы столкнулись с проблемой написания пайплайнов для инфраструктуры. Во всём «виноват» terragrunt: каждому модулю terragrunt нужна отдельная джоба в пайплайне на plan и apply, но для каждого модуля они во многом повторяют друг друга. Подобное постоянное написание одинаковых частей CI/CD пайплайна при добавлении новых баз и бакетов навевало тоску. Рассказываем, как мы создали генератор джоб в Gitlab CI/CD и навсегда забыли о ручном написании пайплайнов для развёртывания элементов инфраструктуры.
https://habr.com/ru/companies/magnit/articles/776214/
#ci/cd #gitlab #gitlabci #terragrunt #terraform #инфраструктура_как_код #пайплайн #автогенерация
☍ https://www.unicorniohater.com.br/snow-day-novo-jogo-de-south-park-ganha-trailer-epico-confira/?feed_id=193712&_unique_id=6560aceb26ba9
Snow Day: novo jogo de South Park ganha trailer épico! Confira
❤ Gostou? Curta e Comenta✌
☑ Marque os amigos.
☑ Ative as notificações.
☑ Siga (@unicorniohater) para continuar recebendo nossos conteúdos ❤!
☛ Acesse o nosso site ☍ www.unicorniohater.com.br e leia a matéria na íntegra ☺.
#brasil #amor #amigos #haters #noite #motivacao #diversao #cerveja #ci...
☍ https://www.unicorniohater.com.br/bastidores-do-filme-garfield-enquanto-a-producao-e-reiniciada/?feed_id=193788&_unique_id=65609f67952ee
Bastidores do filme Garfield enquanto a produção é reiniciada
❤ Gostou? Curta e Comenta✌
☑ Marque os amigos.
☑ Ative as notificações.
☑ Siga (@unicorniohater) para continuar recebendo nossos conteúdos ❤!
☛ Acesse o nosso site ☍ www.unicorniohater.com.br e leia a matéria na íntegra ☺.
#brasil #amor #amigos #haters #noite #motivacao #diversao #cerveja #ci...
How to Install and Configure Jenkins on Windows 11
https://techdirectarchive.com/2023/01/31/how-to-install-and-configure-jenkins-on-windows-11/
#AdminUser, #CI/CD, #ContinuousDeployment, #ContinuousIntegration, #Github, #Jenkins, #JenkinsJob, #JenkinsPipelines, #LocalSecurityPolicy, #LocalSystem, #PortNumber, #Windows11
☍ https://www.unicorniohater.com.br/black-friday-da-ubisoft-jogos-para-pc-com-ate-85-de-desconto/?feed_id=193265&_unique_id=655f5b3b3aaab
Black Friday da Ubisoft: jogos para PC com até 85% de desconto
❤ Gostou? Curta e Comenta✌
☑ Marque os amigos.
☑ Ative as notificações.
☑ Siga (@unicorniohater) para continuar recebendo nossos conteúdos ❤!
☛ Acesse o nosso site ☍ www.unicorniohater.com.br e leia a matéria na íntegra ☺.
#brasil #amor #amigos #haters #noite #motivacao #diversao #cerveja #ci...
Три среды на бэкенде
Я уже не раз порывался написать что-то общее про бранчинг; про некогда распиаренный GitFlow, который запиаривают обратно; про trunk-based development (умеренно распиаривают), про то, как это увязать с разработкой бэкенда. И вот я затираю очередной забуксовавший черновик своей заметки чтобы всё упростить и не гоняться за чрезмерным обобщением опыта. Давайте я просто поделюсь рецептом, а вы его оцените.
https://habr.com/ru/articles/775776/
#бранчинг #бэкенд #среда #environment #staging #production #devops #ci/cd #git #ветвление_git
#contactimprovisation in #kingstonny at Score Dance Studio Sunday! 2 pm. #contactimprovisation #dance #contactimprov #contactdance #danza #contemporarydance #contactimpro #contactimprovisacion #impro #improvisationdance #improv #ci #improvisacion #improvisaciondecontacto #danzacontacto #dancecontactimprovisation #danzaimprovisacion #dancechallenge #quotes #travelling #contactoimpro #quote #danceallday #dancedance #dancealldaylong #improveyourself #improvement #danceeurope #danceyourself
Here's a pic of us dancing in #maltany. #Albanyny #troyny
#contactimprovisation #dance #contactimprov #contactdance #danza #contemporarydance #contactimpro #contactimprovisacion #impro #improvisationdance #improv #ci #improvisacion #improvisaciondecontacto #danzacontacto #dancecontactimprovisation #danzaimprovisacion #dancechallenge #quotes #travelling #contactoimpro #quote #danceallday #dancedance #dancealldaylong #improveyourself #improvement #danceeurope #danceyourself #travel
☍ https://www.unicorniohater.com.br/jujutsu-kaisen-studio-mappa-esta-quebrando-alegacoes-cruciais/?feed_id=191879&_unique_id=655b4a9b1c39b
Jujutsu Kaisen Studio MAPPA está quebrando alegações cruciais
❤ Gostou? Curta e Comenta✌
☑ Marque os amigos.
☑ Ative as notificações.
☑ Siga (@unicorniohater) para continuar recebendo nossos conteúdos ❤!
☛ Acesse o nosso site ☍ www.unicorniohater.com.br e leia a matéria na íntegra ☺.
#brasil #amor #amigos #haters #noite #motivacao #diversao #cerveja #ci...
Czy na pewno wszyscy dobrze korzystamy z NPM, czyli menedżera pakietów Node.js? Ten artykuł być może niektórym uświadomi, że czasem można robić pewne rzeczy nieco inaczej.
https://blog.bitsrc.io/stop-using-npm-install-in-your-ci-cd-pipeline-ba0378bbebfb
Eine einheitliche Gestaltung gehört zu einer funktionierenden Firmenidentität. Wir finden das passende Design gemeinsam mit Ihnen und setzen es für Sie um. #corporatedesign #marketing #firmenidentität #cd #ci #lknienburg #kmu #concepteideen
Fascinating. This ridiculous Gitlab CI issue sees some movement. After 5 years.
Someone decided back in the past that it was a good idea to collapse multi-line CI step commands. Without any way to uncollapse it. 🤦 Really great to debug CI issues (Isn't that fun enough already?).
I subscribed to that issue and the on-and-off there over the years was hilarious 😂
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/3392#note_1654892684
Windows moment
#Programming #SoftwareEngineering #Rust #RustLang #CI #GitHub #Unix
#Typografie wird von vielen Fotograf:innen leider völlig unterschätzt. Dabei ist es nicht nur für ein #Fotobuch oder #Zine relevant, sondern für die ganze #CI: Hausschrift für #Homepage, #SocialMedia, #Flyer etc.
In der neuen Folge vom #StudioKreativkommune #Fotopodcast rede ich mit dem Creative Director Lutz Lungershausen genau darüber.
Shownotes und Links zu allen Podcatchern auf https://studio.kreativkommune.org/podcast
Wir haben ja auf Arbeit ein #SVN-Repo, da ist der #Quellcode drin und wenn "ein Tag" gemacht wird, dann wird:
- #Jenkins-Build #Pipeline abgefahren
- Build-#Artefakte ins Repo committet
- ein SVN Tag erzeugt
Hab heute mit dem #CI verantwortlichen gequatscht und erklärt, Quellcode & Build-Artefakte gehören getrennt, und Build-Artefakte sollten niemals nicht in die #Code-Base aus der sie entstanden sind zurück committet werden.
Musste feststellen, dass der da kein grundsätzliches Problem sieht😐
Using Kaniko instead of Dockers Buildx in GitlabCI
Runners time is down 2min to 35sec.
Ich bin auch optimistisch und setze auf das Klientel der Firmen, Organisationen, Stiftungen, Vereine, Regierungen usw.
In dieser Klientel wird wahnsinnig viel Aufwand getrieben und viel Geld dafür ausgegeben, dass alles einen einheitlichen Look hat. Außer bei den Veröffentlichungen in den Sozialen Medien, da entscheiden dann plötzlich andere über den Look, die Farben, die Schriften.
Wenn sich erst einmal bei dieser Klientel herumspricht, dass bei einem selbst gehosteten Social-Media-Auftritt die Firma auch hier die eigene CI umsetzen kann, sollte es ein Selbstgänger werden, selbst zu hosten - im Fediverse (wo sonst?).
#SocialMedia #CorporateIdentity #CI #Fediverse #Instagram #Facebook
Dear Friends of glass, 🌬️
Thus have I heard:
#Deserts are full of glass. Glass contains water, soup and #Recycling. Glass in a bottle makes music by real intelligences #RI
So precious are our bottle gardens, tended by #CI #Caring Intelligence. In other words prevail by #EI #Example Intelligence. Now make me laugh about Arti fiscal Intelligence. You can abuse a spooky bot if you want …
Як вибрати телевізор для кінотеатру, ігор і не тільки? Поради, приклади та сім важливих нюансів https://itc.ua/ua/articles/yak-vybraty-televizor-dlya-kinoteatru-igor-i-ne-tilky-porady-pryklady-ta-sim-vazhlyvyh-nyuansiv/ #Партнерськийпроект #Телебачення #DolbyAtmos #4KUltraHD #Bluetooth #телевизор #Blu-ray #Thomson #Гейминг #Серіали #HDMI #QLED #Ігри #Кіно #CI+ #DTS #LAN #LED #UHD #USB #4K #AV #HD #ТБ
Exciting - didn't know how easy it was to generate #GitLab #JUnit #ci test files, to precisely see which tests failed!
Sure, the source of the files is a ... Somewhat creatively assembled bash script.
But it works!
We're currently helping set up automated CI simulation of #VHDL using a #GHDL docker image, to verify parts of the #CERN quench detection #FPGA code - and it's looking pretty good so far!
Oh look, #Deezer has a new logo & font and they both _suck_ xD
In my opinion.
I must say, I've been a fan of their old rainbow-colored LED VU Meter. Moving to "amorphous purple heart-shaped blob" is a disappointment.
👋 Developers working on #CollectiveIntelligence and #CivicTech tools, which communities do you love and participate in?
#CI #MultiDisciplinary #CoDesign #Collaboration #ParticipatoryAI #AI #Devs #Development #Coding #Communities
late reply to - what confuses me about #git by a very good explainer of things (can't recall the name or handle)
Just another wrangle with #ci
. It is often useful to consider a checkout to be changing branches, and there are some options that work from that perspective, but they all reference commits.
To checkout a commit has some side effects other than moving HEAD around.
The working directory is updated to the state of the checked out commit.
if a branch name is specified, checkout makes that branch active. The active branch will move along with any new commits that are added.
with the -b option a new branch will be created based on the current commit and then made active.
with the --track option the checked out branch can be made aware of a remote branch
with the --orphan option a new branch is created (like with -b) but will not be based on any existing commit.
Too many rules to remember , yes they make sense but
Weekend project:
Using a local GOPROXY for downloading dependencies blazingly fast in #CI.
In this example, the improvements are dramatic:
Direct download ~10mins
proxy.golang.org 1:20 mins
local proxy: 2.17 seconds
I just realized another reason why fighting #ransomware is so difficult.
It is a #BusinessContinuity issue.
Do you have backups? (Easy to say "yes".) Are they current? (Harder to say "yes".) Do you have a way restore from backup and again function? (Sure, someone tested something once…) Is the procedure to restore current? (How would we know? With all this #agile #CI stuff things change so fast…um, no.)
If we don't design our working systems (we don't), our recovery procedures are doomed.
Wie handhaben das andere hier? Ich bin für #NullToleranz gegenüber #Warnungen im #CI Stack. Da könnte immer ein echtes Problem in der Menge der Warnungen untergehen. Also bitte alles auf 0 durchgehend. Jede Warnung gehört eleminiert.
Und zur statischen Code-Analyse: Die auch auf 0 Warnungen zu kriegen ist spannend aber möglich. Nur dann sollte man die eigenen Tests ausblenden.
On Saturday, I'll have a talk at the Ubuntu Summit about creating a versioned Debian repository that your users can maintain. As many know, maintaining Debian or Ubuntu packages isn't a simple task, but with help from a maintainer, users can help a lot!
https://events.canonical.com/event/31/contributions/259/
So, ein neuer #Container übernimmt jetzt die Aufgabe, den vorher zwei Container in einer völlig absurden historisch gewachsenen Art gemacht haben.
So viel besser isses jetzt zwar auch nicht, aber immerhin mit #CI und nur noch ein #ffmpeg, der gebaut werden muss^^
Reproduzierbar und in meiner Registry, statt irgendwie mit kaputtem Git auf dem Server gebaut...
Steht noch ein anderer aus, aber das geht nicht solange gesendet wird xD
New Arch Linux package: **actionlint** 🐙
🚀 Static checker for GitHub Actions workflow files.
⭐ GitHub: https://github.com/rhysd/actionlint
🐧 Package: https://archlinux.org/packages/extra/x86_64/actionlint/
#github #actions #ci #automation #linter #go #archlinux #linux #commandline
And the last two releases saw GHA/AP improve their lead:
2022: Python 3.11
🥇 a day: @github Actions ↔️
🥈 2 days: Azure Pipelines ↔️
🥉 14 days: AppVeyor ↔️
4️⃣ 28 days: Travis CI ↔️
2023: Python 3.12
🥇 13 hours: @github Actions ↔️
🥇 13 hours: Azure Pipelines ↔️
🥉 20 days: Travis CI ⬆️
4️⃣ 28 days: AppVeyor ⬇️
And GitHub Actions already has 3.13 alpha available!
#Python #CI #CImedals #medals #GitHubActions #AzurePipelines #TravisCI #AppVeyor #Python311 #Python312 #Python313
In 2019-2021, here's how long it took CI services to support the newest Python release:
2019: Python 3.8
🥇 21 hours: Travis CI
🥈 20 days: @github Actions
🥉 24 days: Azure Pipelines
4️⃣ 25 days: AppVeyor
2020: Python 3.9
🥇 17 hours: @github Actions ⬆️
🥈 20 days: Travis CI ⬇️
🥉 21 days: AppVeyor ⬆️
4️⃣ 22 days: Azure Pipelines ⬇️
2021: Python 3.10
🥇 12 hours: @github Actions ↔️
🥈 17 days: Azure Pipelines ⬆️
🥉 28 days: AppVeyor ↔️
4️⃣ 106 days: Travis CI ⬇️
would anyone be interested in remote access to any of the following devices for the purposes of #Linux mainline development and testing? You'd be able to power cycle the device and boot an Android boot.img (kernel + dtb + ramdisk), I'm also open to using these devices in CI
* OnePlus 6/6T - #Qualcomm Snapdragon 845
* OnePlus 7 and/or 7 pro - #Qualcomm #Snapdragon 855 / sm8150
* OnePlus 9 Pro - Snapdragon 888 (sm8350), however i haven't yet found out how/if UART is exposed on this device.
* Google Pixel 2 XL, 3, or 3 XL - Snapdragon 835 (msm8998) or Snapdragon 845 (sdm845). (Only have one usb-cereal adapter so only one of these is viable right now)
* #Fairphone 2 - MSM8974
* #Fairphone 5 - QCM6490
* #LG G6 - msm8996 (if someone can find UART and find a workaround for the "charger wet" detection being stuck on)
* #Samsung j3 (j3xnlte) - some spreadtrum SoC - Only if you can find UART for me
I don't have things fully set up here but I'm trying to figure out what i should prioritise.
If any of these sounds useful to you then please get in touch with me! I'm especially interested in folks from the #LinuxMobile community, #Kernel maintainers, or anyone else with an interest in upstream Linux support on phones. Please have some kind of public presence in a related field and tell me what your usecase is.
* DM me on matrix - @ caleb:postmarketos.org
* Email me - caleb@connolly.tech
Please boost for reach!
#FOSSMobile #postmarketOS #Android #Embedded #BoardFarm #Testing #CI
I wrote a blog post about "**Fully Automating Releases for Rust Projects**" 🦀
✨ Read here: https://blog.orhun.dev/automated-rust-releases
🚀 Repository: https://github.com/orhun/automated-rust-releases
💖 Shoutouts: @MarcoIeni (`release-plz`), axo.dev (`cargo-dist`), @github (dependabot), mergify.com, git-cliff.org
Most #CI systems, like #Travis, #jenkins and GitHub Actions both run the test suite on every branch after it's pushed to and every pull request when it's opened, and #GitHub can block the pull requests if the tests fail on them. To understand why this is insufficient to get an evergreen main branch
https://bors.tech/devdocs/bors-ng/readme.html
Unfortunately, parse_signature_lines() in pretty.c, which references a simple mapping in struct signature_check, will blissfully ignore the warning and match only "Good signature from", yielding “G”. A patch to provide a separate token for untrusted keys is simple, but for the time being, we will explore two separate implementations—one that will parse the simple one-line output that is ignorant of trust and a mention of a less elegant implementation that parses the GPG output
#Git does most of the work for us! If a ref is provided, it will be converted into a range spec by appending ".." (e.g. a1b2c becomes a1b2c..), which will cause git log to return all of its children (not including the ref itself). If no ref is provided, we end up using HEAD without a range spec, which will simply list every commit (using an empty string will cause Git to throw an error, and we must quote the string in case the user decides to do something like "master@{5 days ago}"). Using the --pretty option to git log, we output the #GPG signature result with %G?, in addition to some useful information we will want to see about any commits that do not pass the test. We can then filter out all commits that have been signed with a known key by removing all lines that end in “G”—the output from %G? indicating a good signature.
we can either check the output itself or check the exit status of the script, which indicates a failure. If this script were run by a CI system, the best option would be to abort the build and immediately notify the maintainers of a potential security breach (or, more likely, someone simply forgot to sign their commit).
careful when running this script directly from the repository, especially with CI systems—you must either place a copy of the script outside of the repository or run the script from a trusted point in history. For example, if your #CI system were to simply pull from the repository and then run the script, an attacker need only modify the script to circumvent this check entirely.
with command here (cf 1)a larger repository, all unique keys will be listed. Note that the above example does not specify any range of commits; you are free to integrate it into the signchk script to use the same range, but it isn’t strictly necessary (it may provide a slight performance benefit, depending on the number of commits that would have been ignored)
there is a huge difference between the conventional use of trust with PGP/GPG (“I assert that I know this person is who they claim they are”) vs trusting someone to commit to your repository. As such, it may be in your best interest to maintain an entirely separate web of trust for your CI server or whatever user is being used to perform the signature checks.
Although is not a #Git constraint it is a common practice. #GitLab
seems to do exactly the same
based on the #weboftrust established from the public keys directly trusted by the #CI system, you could then automatically determine whether or not a commit can be trusted even if the key was not explicitly placed on the serve. Given reference commit r (optionally empty), let C′ be the set of all first-parent commits such that C′ = r..HEAD (range spec) and let K be the set of all public keys in a given GPG keyring. We must assert that, for each commit c in C, there must exist a key k in keyring K such that k is trusted and can be used to verify the signature of c. This assertion is denoted by the function g (GPG) in the following expression: ∀c ∈ C′g(c).
#github
https://secure-git.guide/010_GPG-Git-commits-partially-verified/
HNNNNNGGHHH.
I solved it.
The Jenkins (and Drone) build agent launched in intel mode rather than arm, so all subprocesses were also running through Rosetta or something.
Made sure to have an OpenJDK (whatyearisit.gif) that ran in native arm mode, and everything went back to normal.
I'm still not sure why this started happening when I updated XCode, but I can't be bothered to think more about this now.
Plot Twist: Tried setting up a build using drone.io - and it's just as slow as Jenkins. But plain ssh still works fine.
Wat?
Is there something that runner agents universally do when launching stuff that somehow interferes with clang?
Python 3.13 alpha 1 was released on Friday and GitHub Actions added it on Monday 🚀
If you're up for some early testing, here's how:
https://github.com/actions/setup-python/issues/742#issuecomment-1764118264
Meanwhile, Travis CI still don't have 3.12.0 final, they're still beta 1+ from May, 2023...
https://app.travis-ci.com/github/hugovk/test/jobs/611062434#L212
https://travis-ci.community/t/add-python-3-12/14006?u=hugovk
#Python #Python3.12 #Python3.13 #GitHubActions #CI #GitHub #TravisCI
I finally managed to make a #rootless #Podman #Quadlet for #Gitlab that is functional on local setups and includes #GitlabRunner to run #ContinuousIntegration / #CI on!
The Readme mentions all the needed steps to run it, avoiding all the gotchas that you might encounter.
Internally the Gitlab Runner can use #Docker containers from within Podman without any issues!
This makes it much easier for you to learn how to do CI yourself.
https://github.com/herzenschein/herz-quadlet/tree/main/gitlab
I've blogged previously about Python Packaging and described how to automate publishing to PyPI when your project is hosted on GitHub.
I've now worked out how to do this from GitLab and so have written that up too...
nix build -f ciHomeManagerConfigurations.nix
https://ipetkov.dev/blog/tips-and-tricks-for-nix-flakes/
#ci #homemanager
My friend Sean Miller has a blog post up : Adding GitHub Actions to Run RSpec and SimpleCov https://thewanderingcoder.com/2023/09/adding-github-actions-to-run-rspec-and-simplecov/ with repect to (as it says on the tin) #Ruby, #GithubAction #Rspec #SimpleCov and #CI
@slackline I had the same thought as @manu_faktur: have you protected the tags that you're trying to make releases for? (but I posted before realizing we had the same thought, whoops, so editing in an attempt to recover 😛 )
Also, this is kind of beside the point but you may be interested in the --non-interactive option to twine. If nothing else it might make the error message a bit more clear when something like this happens.
Got a problem with GitLab CI and Variables not being shown on pipelines triggered by $CI_COMMIT_TAG
If anyone has experience/ideas details are at
https://forum.gitlab.com/t/ci-variables-missing-when-triggering-build-based-on-tag/93309
What are folks using for #selfhosted #ci these days?
@benjaminhirsch you miss the fastest and most fun one! CodeIgniter (https://CodeIgniter.com).
My article on how to test the Python 3.12 release candidate was on @pythonbytes!
https://www.youtube.com/live/1zf29sQVGow?t=444
"You basically have a couple of days to make sure that your library will have no hiccups when Python 3.12 ships in a week. You want to make sure that your stuff just works, so here's your chance and a few steps on how to do that."
https://dev.to/hugovk/help-test-python-312-beta-1508/
#python #python312 #ReleaseCandidate #RC #test #CI #GitHubActions
I do hate testing GitHub Pipelines. If I need as example debug the last step of the pipeline I need to wait around 6 minutes to reach that exact step. If I reach the step I need to wait until the critical part is getting triggered just to see I did another spelling mistake and it's still broken.
Trying to include a installer into one of my projects for 2 hours now, waiting most of the time to hit the exact step ...
"#Python 3.6.x will be removed from Ubuntu 20.04 and Windows 2019 images.
"The motivation for the changes
"As per our software support policy, we are supporting only 5 most popular python versions while python 3.6.x has been #EOL since 2021/12/23.
"Possible impact
"If your projects depend on python 3.6.x they might be broken.
"Mitigation ways
"For #GitHubActions the python 3.6.x archives will still be available through the actions/setup-python action"
https://github.com/actions/runner-images/issues/8238
#Python36 #CI
Alles für die #CI - auch bei der @medienkuh #442. Es war schön mit Ihnen, Herr @dominikhammes, aber Herr @koerber freut sich auch schon auf den Kuchen!😉 #Nachklapp
Hello again #Python library maintainers! 🐍
Because everyone was so good at finding bugs last time (thank you!), we're getting a bonus release candidate! 🎉
🚨🚨 The third and final Python 3.12 RC is out now! Please give it a spin, it's the last chance to find critical problems.
How to test:
https://dev.to/hugovk/help-test-python-312-beta-1508
More info:
New blog post: Pulsar's CI
A look into the significant ways that Pulsar's CI has recently changed. The why and how behind what happened.
https://pulsar-edit.dev/blog/20230903-confused-Techie-pulsars-ci.html
Hello #Python library maintainers! 🐍
The second and final Python 3.12 release candidate is out! 🎉
🚨 This means we have under a month before the big release on 2023-10-02 to test our packages and get them ready. And we might help iron out last-minute bugs in Python itself!
I've updated my how-to-test guide:
https://dev.to/hugovk/help-test-python-312-beta-1508
More info:
https://discuss.python.org/t/python-3-12-0rc2-final-release-candidate-released/33105?u=hugovk
Want a nice _and_ reliable #calendar application for #GNOME and #Linux desktops (& #mobile!) in general, based on the @EvolutionGnome data server?
Know some #C #programming and looking for a well-scoped challenge to get your feet wet and put those skills to use in #opensource?
#GNOMECalendar could really use your help to write unit tests, so that we can use #TestDrivenDevelopment #TDD #CI for #refactoring all timezones-related code and make it reliable. Now is the time!
https://fortintam.com/blog/call-for-help-writing-gnome-calendar-compliance-unit-tests/
Github actions are designed with no CPU efficiency in mind.
It terrifies me how much time Github actions spent doing same things again and again in cases where it could easily be mitigated by cache and a good CI system design that targeted to spent resources effectively in general.
Unsurprisingly Github Actions billing is based on minutes spent repeatedly doing those things.
#Github #GithubActions #GiveUpGitHub #CI #CarbonEmissions #CorporateGreed
I'm curious if anyone has written about a strategy for fixing bugs in a way that retains the integrity and usability of the code base beyond #TDD and #CI? As my role sunsets, I'm thinking about how I can set the next maintainers of my packages up for success so that patches can be made in a way that does not break workflows ten iterations in the future due to patches piled upon patches.
Relevant XKCD: https://xkcd.com/1172/
We ran out of free #GitLab #CI minutes this month and I've just had to fix a linking error in #inkscape main caused by not having code compiled before being merged.
This is a good and bad sign. We're hitting the limits of the resources the project has at it's disposal because our activity this month has been very high with the paid #Gtk4 migration work.
Some of the new code from our contract workers is looking really good by the way. Lots of valuable cleanup along with fixing the core issues with the upgrade.
#foss #project #opensource #softwarefreedom #sfconservancy #git
Currently running Jenkins but kind of hate it and every three months or so I start googling alternatives until I feel that it _does_ actually do what we need and I don't feel like setting up something new that's probably just as horrible.
Having a look at TeamCity though and it does seem to check a lot of the right boxes. What say ye? Yay? Nay?
#softwareengineering #BuildAutomation #ci #teamcity #jetbrains
Got a proof-of-concept of sitespeed.io (https://www.sitespeed.io/) working in a Gitlab CI process without having to run docker in docker and without having to use the premium-only snippet (https://docs.gitlab.com/ee/ci/testing/browser_performance_testing.html#configuring-browser-performance-testing)
Blog post coming soon!
Today marks an awesome milestone!
Our v1.0.0 just got #released out into the wild.
Catch it if you can ... and play around, it got a ton of improvements over our old versions.
Also please #boost so everybody notice it.
#WoodpeckerCI #cicd #release #SelfHosting #awesome #coding #ci #cd
https://github.com/woodpecker-ci/woodpecker/releases/tag/v1.0.0
If you have experience maintaining a GitLab CI runner on macOS, and you wish to contribute to building and testing GLib and GTK on macOS, please join the GNOME Infrastructure channel to help maintaining the macOS server provided by the GNOME Foundation, otherwise we will have to retire it. More details on Discourse: https://discourse.gnome.org/t/potential-retirement-of-the-macos-ci-builder-for-glib-and-gtk/16198
Part of today has been taken up putting together an additional @snappautomotive #CI server for our #AAOS #AOSP builds and our #Android apps. It still blows my mind that these 40 Core / 80 Thread machines with 256GB of RAM cost around 1k GBP.
Personally I find putting the machine together pretty relaxing… right up until I have to power it on 😁
Today is the last day for you to share how your team is delivering and operating software. Our annual, anonymous, platform-agnostic survey closes at 11:59PM PT.
This year's survey is available in English, Español, Français, Português, and 日本語.
A 15 minute investment will provide insights to the entire industry.
We are providing access to our #WoodpeckerCI instance to those who need it, some caveats still apply.
Also, you can read about the upcoming #ForgejoActions.
Check out our docs to learn more about the state of CI on Codeberg: https://docs.codeberg.org/ci/
And Python 2.7 is now gone from GitHub Actions! 🪦
https://github.com/actions/setup-python/issues/672#issuecomment-1602673800
11% of companies be like ¯\_(ツ)_/¯
🙈
#CI #CICD #UnitTest #Testing #Automation #Stackoverflow #StackoverflowSurvey #WhatCanGoWrong #SoftwareEngineering
Calling all #Python library maintainers! 🐍
Python 3.12 is in beta! 🎉
This means no new features are allowed in and it's now time to start testing your code. You might find things in your code to fix, or even better, you might find things to fix in Python itself!
Here's how to do it:
https://dev.to/hugovk/help-test-python-312-beta-1508 #python312 #beta #test #CI #GitHubActions
“From development environments to continuous integration—the ultimate guide to software development with Guix”
https://guix.gnu.org/en/blog/2023/from-development-environments-to-continuous-integrationthe-ultimate-guide-to-software-development-with-guix/
Next, GitHub will be removing support for Python 2.7 from actions/setup-python in under a month, on 19th June. 🪦
"Breaking changes
"Hello everyone. The Python 2.7.x will be removed from python-versions and it won't be possible to set up Python 2.7.x by setup-python.
"The motivation for the changes
"Python2.7 is not supported since January 1, 2020."
How to reduce your devops tool sprawl - After spending the last decade investing in devops, many companies are experiencing a ... - https://www.infoworld.com/article/3696271/how-to-reduce-your-devops-tool-sprawl.html#tk.rss_all #versioncontrolsystems #softwaredevelopment #applicationsecurity #developmenttools #devops #ci/cd
This month we have iconography updates, symbols-view improvements, CI upgrades and bunch of upgrades to our package backend and website.
Check out the latest community update on the Pulsar Blog!
https://pulsar-edit.dev/blog/20230501-Daeraxa-MayUpdate.html
#opensource #opensourcedev #CommunityDevelopment #CI #packagedevelopment #communitypackages #website #pulsar #pulsaredit
After a month+ of hacking on #GithubActions and I'm in a right mix about it. Great for building, but I'm unconvinced on using it for deployment.
Even with Merge Queue, and trunk-based development, I struggle with good patterns for roll out, roll back, promotion etc etc.
All thoughts and links welcomed.
I've written recently how a slow CI/CD kills productivity.
We got to cut both of our #CI and #CD times in half, and the difference is huge.
However, it's not yet enough.
CI/CD must be FAST.
It's not just #developer #productivity. It's also your time to recover from a #production issue.
The pandoc #Docker images make it easy to process documents on #CI systems like GitLab CI and GitHub Actions.
Docs: https://gitlab.com/pandoc/pandoc-ci-example
https://github.com/pandoc/pandoc-action-example
In between Vim research, for the past few weeks I've been kicking the tires on Skylounge -- a tool for managing pipelines in Github Actions.
It addresses many of the problems I'm familiar with from Cloud Foundry -- how can we build & deploy lots of applications quickly & securely? -- but from a different angle.
They've got a demo coming up on May 4. If you're wrestling your CI automation or your security & compliance requirements, sign up!