Recent Blog Posts

Earlier this month, a full-day event about Jenkins Pipeline was organized in Toulouse, France with the Toulouse JAM. After a warm-up on the previous Tuesday where Michaël Pailloncy had given a talk at the local Toulouse Devops user group about Jenkins Pipeline ecosystem, we were ready for more digging :-). The agenda We had planned the day in two parts: Morning would be a more driven workshop with slides & exercises to be completed Pizzas & beverages to split the day :-) Afternoon would be somehow like an Unconference, where people basically decide by themselves what they want to work on. We planned to have 30 attendees. We ended up having 25. We considered having more people, but finally decided that for a first time it would be better to start not too big. Infrastructure Infrastructure was sponsored by DigitalOcean. For each attendee, we provisioned : One Controller, preconfigured to be able to dynamically provision agents. One staging environment One production environment [ 1 ] One SonarQube instance Workshop content & infrastructure After an initial quick presentation to settle context and remind some general things about Continuous Delivery and Jenkins, we started the workshop per se. It is composed of 3 parts, which are readable here [ 2 ], but very few people were able to start the part 3. Hackergarten / Unconference So we let people decide what they wanted to work on during the afternoon. We decided to use post-its: each attendee would write down what they wanted to work on, one idea per post-it (max 2 per person). Then, we dropped those onto a white-board and tried grouping those by theme. In the end, overall, the following themes went out: Hack on Jenkins development & Contribute to Jenkins Complete the workshops Work on use-case oriented things Work on Docker & Pipeline join usages Hackergarten Many Jenkins accounts were created, and many JIRA and pull requests were filed. It was nice to see people asking questions like: "so, should I create a JIRA issue for this?" or "how do I interact with people". Pretty generic "how do I work on open source software" questions sometimes, but important because you felt like people were genuinely interested and needed not much to start contributing. Here are the pull requests filed during this afternoon: blueocean-pipeline-editor-plugin#30 jenkins#2785 jenkins#2786 jenkins#2787 jenkins#2788 You can see that though most of the PRs were typo-related, the one that got merged first was the one about code :-). So, Jeremie Violas wins the Bobble Head as promised! Why so many typo-related PRs? Simply because people were somehow encouraged to find some to get used to the round trip of: fixing an issue and filing the associated pull request, rinse & repeat. I do think this is also a pretty nice and simple first step to understand how to build Jenkins and start interacting with the community. The result People seemed pretty happy and we got some nice comments like "now I have a clearer vision of what this Pipeline thing is about". Some attendees also dropped nice comments on the meetup page. So it’s cool because when you’re doing such things on your free time, it’s the main reward you can get. If you’re an attendee to such events, don’t forget to thank people organizing those, and more importantly to provide constructive feedback. We are generally eager to know what could be done better for next time. Conclusion Overall we are very happy with the energy of that day, and we definitely plan to set up a new session in the next few months, probably with a bit more people. Some thoughts: Infrastructure: when you plan to have many VM per attendee, double-check the limits your Cloud Provider may have by default. I had bumped it to 250 the day before the workshop, and asked for another one to 500 during the workshop (though in the end, 250 was probably enough, but this’ll give room for the next time with more people :-)). Logistics: warning, secret ahead: this is very time consuming. Not necessarily the amount of work itself, more that it implies very big latency. For instance, give it 2 to 3 weeks minimum to have answers about sponsoring in general. Pinging again in case of no answer after 2 days would probably be seen as rude, and possibly lead to make things worse for obvious reasons, so plan ahead. Thank you DigitalOcean for sponsoring the Infrastructure We got way more than 100 VMs running at the same time during the day thanks to their help! HarryCow Coworking for hosting the event To CloudBees for sponsoring the food for all the participants Also for providing a bunch of goodies: stickers and T-Shirts for everybody GitHub for providing stickers 1. For the sake of the simplicity of the workshop, those environments were actually a single VM: the goal was here to illustrate what we could do using Jenkins Pipeline, discussing scalability or more involved deployment techniques was obviously out of scope. 2. in French only for now, but translating it into English to make it possibly shared and reusable among JAMs is being discussed

As we near the end of the year, the number of November JAMs show that the Jenkins community isn’t slowing down for holiday season. We had a number of excellent events hosted around the world this November with plenty of great stories and presentations shared by the various members of the world-wide Jenkins community. Melbourne, Australia JAM Melbourne JAM leaders, Raisa and Bhuva hosted Blue Ocean for the inaugural meeting. Attendees learned the values of Blue Ocean, a project that rethinks the user experience of Jenkins, modeling and presenting the process of software delivery by surfacing information that is important to development teams with as few clicks as possible, while still staying true to the extensibility that Jenkins always has had as a core value. Thank you James Dumay for stopping by to take part in the inauguration. Singapore, Singapore JAM One of the members who had several years of experience using Jenkins (since Hudson days in fact) to present some basics on Continuous Integration with GitHub. It was targeted at new members who are starting out with Jenkins. We understand that we cannot always serve advanced topics to cater to the experienced users and neglect the newbies so this session was targeted to help give new users an introduction to Jenkins. It went well with about 15-20 attendees and we hope to run some hands-on workshops in 2017. Some members were looking forward to freebies like stickers and T-shirts too! Moscow, Russia JAM Moscow JAM leaders, Kirill Tolkachev and Oleg Nenashev led the inaugural meeting with a packed full agenda. Oleg began the meeting with an update on Jenkins 2 what improvements users can expect and what enhancements are in the works within the Jenkins project. Following Oleg, Kirill shared how his team in Alfa Laboratory used Jenkins to improve CD/DevOps in their projects (with Jenkins Pipeline, Job DSL and Blue Ocean), the problems they experienced and how they fixed them. Then Oleg talked about Jenkins Pipeline internals, main features and recent changes in the ecosystem. It was followed up by a discussion of large-scale Jenkins instances at the after-party. The recording of the event can be found on YouTube. Milan, Italy JAM The first meetup was a great opportunity to meet local Jenkins fans to learn and share Jenkins experiences at a local cafe. San Francisco, California JAM R. Tyler Croy performed a 30 minutes live Pipeline coding demo to a relatively novice audience (though all had used Jenkins). A good amount of questions from the audience which conveyed an appetite for the content being presented. Ryan Wallner, presenter from ClusterHQ, also gave a demo based around Pipeline talking about ClusterHQ’s "Fli" integration with a delivery pipeline. Washington, DC JAM There was a fantastic 90% showup rate at this month’s meetup - 58 RSVPs and 52 in attendance was pretty impressive. All this may be due to Fannie Mae’s story - the success of how they used Jenkins for CI/CD as part of their DevOps adoption. Afterwards, there was a lot of interests and further discussions taking place. Next month’s host will be Freddie Mac. Seattle, Washington JAM Long time Jenkins community member and Seattle JAM leader, Khai Do showed how OpenStack uses "Jenkins Job Builder" to manage and run thousands of Jenkins jobs per day in their multi-controller CI/CD system. He also compared Jenkins Job Builder with other Jenkins "Infrastructure-as-code" technologies - Jenkins Pipeline and Jenkins JobDSL. It was followed by an in-depth Q&A and discussion session. Dallas/Forth Worth, Texas (DFW) JAM The November DFW JAM was the most strongly attended of the year! DFW JAM leader, Eric Smalling discussed the benefits of dynamic build agents and demonstrated various ways to implement them such as the EC2 and Docker plugins. There was a lot of interest and discussion, especially around Docker and the ability it provides to have ephemeral agents with very little provisioning time. The recording can be downloaded from Gooel Drive. Links Start a JAM in your city if there isn’t one already. Become a JAM member. Become an online JAM member Be a JAM speaker or sponsor. Let us know jenkinsci-jam@googlegroups.com Become a Jenkins project contributor

October has proven to be a busy month within the Jenkins Area Meetup groups. Below is a recap of topics discussed at various JAMS in the month of October. Dallas Forth Worth, Texas (DFW) JAM James Dumay took time out of his vacation to present Blue Ocean, a project that rethinks the user experience of Jenkins, modeling and presenting the process of software delivery by surfacing information that is important to development teams with as few clicks as possible, while still staying true to the extensibility that Jenkins always has had as a core value. See recording HERE. San Francisco, CA JAM Andrey Falko from Salesforce shared how he and his Diagnostics team used Jenkins to deliver software securely and reliably to production within Salesforce. See videos HERE and HERE. Boulder, CO JAM This was a meetup with CA Technologies and included Mark Waite, maintainer of the Jenkins git plugin and a director at CA Technologies in Fort Collins. Tyler did a great presentation about Jenkins Pipeline and Blue Ocean and showed off how the community is using Blue Ocean to build Jenkins. Barcelona, Spain JAM At this meetup, there were plenty of engaging discussions surrounding the Jenkins Certification and DevOps 2.1 Toolkit: Continuous Deployment with Jenkins and Docker Swarm. Guillem Sola shared his Jenkins certification experience HERE while Viktor Farcic presented his thoughts on the aspects of building, testing, deploying, and monitoring services inside Docker Swarm clusters and Jenkins https://www.youtube.com/watch?v=fs1ED_y5mUc. Lima, Peru JAM October’s meetup was a joint effort with collaboration from Perú JUG, and Docker Lima. The first talk was an Introduction to Docker Ecosystem, second was Building and Testing Apps with Docker and Arquillian Cube and the last one was CI/CD using Docker and Jenkins Pipelines. We had a full house at the meetup. Now, everyone in the room has a Mr. Jenkins branded on their laptop :) Special thanks to Mario Inga and Héctor Paz for their collaborations during the last meetups. Links Start a JAM in your city if there isn’t one already. Become a JAM member. Become an online JAM member Be a JAM speaker or sponsor. Let us know jenkinsci-jam@googlegroups.com Become a Jenkins project contributor

On September 6th we had a Jenkins Online Meetup. This meetup was the second event in the series of Plugin Development meet ups. At this meetup we were talking about Jenkins Web UI development. Talks 1) Classic Jenkins UI framework - Daniel Beck In the first part of his talk, Daniel presented how Stapler, the web framework used in Jenkins, works, and how you can add to the set of URLs handled by Jenkins. In the second part he was talking about creating new views using Jelly and Groovy, and how to add new content to existing views. Keywords: Stapler, Jelly, Groovy-defined UIs 2) Developing modern Jenkins UIs with Javascript - Tom Fennelly Feel that Jenkins UI is a bit old? You are not alone. In addition to the old stack Jenkins offers a framework for writing UI components in Javascript with help of Node.js. Tom presented this new engine, which is being used in new Jenkins Web UI components like Jenkins installation wizard. He also provided several examples from the BlueOcean project he is working on. Keywords: Node.js, ReactJS, Jenkins JS Builder, Jenkins Design Language, Blue Ocean Links Meetup page Event page: Plugin Development. Web UI Webinar recording Want to conduct a meetup? We are looking for speakers, who would be interested to share their experience about Jenkins best-practices, war stories and plugin development. If you are interested to conduct a presentation, please contact meetup organizers using meetup.com “contact organizers” feature or via the events@lists.jenkins-ci.org mailing list.

Recently, the Jenkins project announced the release of Jenkins 2.0, a first major release after 10 years and 655 weekly releases. This has been a major milestone for Jenkins and its growing community of developers, testers, designers and other users in the software delivery process. With its rising popularity and wide adoption, the Jenkins community continues to grow and evolve into the millions. Jenkins community meetup activity has risen to an all time high since the first Jenkins meetup which was established on August 23 2010, in San Francisco. Over the last six months the number of Jenkins Area Meetup (JAM) Groups has grown from 5 to 30, with coverage in Asia, North America, South America and Europe. That’s an average growth of 4 new JAMs per month. As of today, there are over 4,100 Jenkins fans within the Jenkins meetup community. This is the result of contributions from community JAM leaders who have volunteered their time to provide a platform for learning, sharing and networking all things Jenkins within their local communities. For anyone who has not organized a meetup before, there are many moving parts that have to come together at a specific location, date and time. This process takes significant effort to methodically plan out. From planning the food and beverages to securing speaker(s), a venue, audio/visual setup, technical logistics and of course promoting the meetup. It does takes a level of passion and effort to make it all happen. Many THANKS to the 55 JAM leaders, who share this passion - they have successfully organized over 41 meetups within the past six months in North America, South America and Europe. That’s about 6 meetups a month! There are still plenty of opportunities to be a JAM organizer. If there is not a JAM near you, we’d love to hear from you! Here’s how you can get started.

A few weeks ago, my colleague Brian Dawson and I were invited to present on Scaling Jenkins for Continuous Delivery with Microsoft Azure in Microsoft’s Reactor space. Azure is Microsoft’s public cloud offering and one of the many tools available to Jenkins users for adding elastic compute capacity, among other things, to their build/test/deploy infrastructure. While our presentations are applicable to practically any cloud-based Jenkins environment, Thiago Almeida and Oguz Pastirmaci from Microsoft were also on-hand and presented some interesting Azure-specific offerings like Azure Container Service with Jenkins. While we do not have video from the meetup, Brian and I did record a session with Thiago and Oguz for Channel9 which covers much of the same content: To kick-off the meetup we asked attendees a few polling questions and received very telling responses: How big is your Development/IT organization? What is your role? By show of hands do you practice CI/CD/DevOps/etc? At what scale (tooling and practice)? The responses indicated that the majority of attendees were from small to medium organizations where they practiced Continuous Delivery across multiple teams. A notable 25% or greater attendees considered themselves "fullstack" or participating in all of the roles of Developer, QA, and Operations. Interesting when paired with the high number (~80%) of those who practice CD. This is likely because modern teams, with mature CD practices, tend to blur the traditional lines of Developer, QA and Operations. However, In my experience, while this is often the case for small to medium companies in large organizations team members tend to fall into the traditional roles, with CD providing the practice and platform to unify teams across roles. — Brian Dawson After gauging the audience, Thiago and Brian reviewed Continuous Delivery (CD) and implementing it at scale. They highlighted the fact that CD is being rapidly adopted across teams and organizations, providing the ability: to deliver a demonstrably higher quality product, shipping more rapidly than before, and to keep team members happier. However, when organizations fail to properly support CD as they scale, they run into issues such as: developers acting as administrators at the cost of productivity, potential lack of security and/or exposure of IP and difficulty in sharing best practices across teams. Thiago then highlighted that properly scaling CD practices in the organization along with the infrastructure itself can alleviate these issues, and discussed the benefits of scaling CD to on cloud platforms to provide "CD-as-a-Service." Overall I found the "theory" discussion to be on point, continuous delivery is not just a technology nor a people problem. Successful organizations scale their processes and tooling together. The slides from our respective presentations are linked below: (Brian) Scaling Jenkins for Continuous Delivery (.pdf) (Tyler) Scaling Jenkins with Azure (.pdf) I hope you join us at future San Francisco JAM s!

Last week we hosted our first ever Online JAM with the debut topic of: Jenkins 2.0. Alyssa, our Events officer, and I pulled together a series of sessions focusing on some of the most notable aspects of Jenkins 2 with: A Jenkins 2.0 keynote from project founder Kohsuke Kawaguchi An overview of "Pipeline as Code" from Patrick Wolf A deep-dive into Pipeline and related plugins like Multibranch, etc from Jesse Glick and Kishore Bhatia An overview of new user experience changes in 2.0 from Keith Zantow A quick lightning talk about documentation by yours truly Wrapping up the sessions, was Kohsuke again, talking about the road beyond Jenkins 2.0 and what big projects he sees on the horizon. The event was really interesting for me, and I hope informative for those who participated in the live stream and Q&A session. I look forward to hosting more Virtual JAM events in the future, and I hope you will join us! Questions and Answers Below are a collection of questions and answers, that were posed during the Virtual JAM. Many of these were answered during the course of the sessions, but for posterity all are included below. Pipeline What kind of DSL is used behind pipeline as code? Groovy or allow freely use different languages as a user prefer? Pipeline uses a Groovy-based domain specific language. How do you test your very own pipeline DSL? Replay helps in testing/debugging while creating pipelines and at the branch level. There are some ideas which Jesse Glick has proposed for testing Jenkinsfile and Pipeline libraries captured in JENKINS-33925. Isn’t "Survive Jenkins restart" exclusive to [CloudBees] Jenkins Enterprise? No, this feature does not need CloudBees Jenkins Enterprise. All features shown during the virtual JAM are free and open source. CloudBees' Jenkins Enterprise product does support restarting from a specified stage however, and that is not open source. How well is jenkins 2.0 integrate with github for tracking job definitions? Using the GitHub Organization Folder plugin, Jenkins can automatically detect a Jenkinsfile in source repositories to create Pipeline projects. Please make the ability for re-run failed stages Open Source too :) This has been passed on to our friends at CloudBees for consideration :) If Jenkinsfile is in the repo, co-located with code, does this mean Jenkins can auto-detect new jobs for different branches? This is possible using the Pipeline Multibranch plugin. What documentation sources are there for Pipeline? Our documentation section contains a number of pagesaround Pipeline. There is also additional documentation and examples in the plugin’s git repository and the jenkinsci/pipeline-examples repository. (contributions welcome!) Where we can find the DSL method documentation? There is generated documentation on jenkins.io which incldues steps from all public plugins. Inside of a running Jenkins instance, you can also navigate to JENKINS_URL/workflow-cps-snippetizer/dslReference to see the documentation for the plugins which are installed in that instance. If Pipeline is not support some plugins (there is a lot actually), I needed SonarQube Runner but unfortunately it’s not supported yet, in Job DSL plugin i can use "Configure Block" and cover any plugin via XML, how i can achieve the same with a Pipeline? Not at this time Is there a possibility to create custom tooltips i.e. with a quick reference or a link to internal project documentation? Might be useful i.e. for junior team members who need to refer to external docs. Not generally. Though in the case of Pipeline global libraries, you can create descriptions of vars/functions like standardBuild in the demo, and these will appear in Snippet Generator under Global Variables. Oh pipeline supports joining jobs? It’s really good, but I cannot find document at https://jenkins.io/doc/ could you tell me where is it? There is a build step, but the Pipeline system is optimized for single-job pipelines We have multiple projects that we would like to follow the same pipeline. How would I write a common pipeline that can be shared across multiple projects. You may want to look at implementing some additional steps using the Pipeline Global Library feature. This would allow you to define organization-specific extensions to the Pipeline DSL to abstract away common patterns between projects. How much flexibility is there with creating context / setting environment variables or changing / modifying build tool options when calling a web hook / api to parameterize pipelines for example to target deployments to different env using same pipeline Various environment variables are exposed under the env variable in the Groovy DSL which would allow you to construct logic as simple or as complex as necessary to achieve your goal. When you set up the job for the first time, does it build every branch in git, or is there a way to stop it from building old branches? Not at this time, the best way to prevent older branches from being built is to remove the Jenkinsfile in those branches. Alternatively, you could use the "include" or "exclude" patterns when setting up the SCM configuration of your multibranch Pipeline. See also JENKINS-32396. Similar to GitHub organizations, will BitBucket "projects" (ways of organizing collections of repos) be supported? Yes, these are supported via the Bitbucket Branch Source plugin. How do you handle build secrets with the pipeline plugin? Using unique credentials stored in the credentials plugin per project and/or branch? This can be accomplished by using the Credentials Binding plugin. Similar to GitHub Orgs, are Gitlab projects supported in the same way? GitLab projects are not explicitly supported at this time, but the extension points which the GitHub Organization Folder plugin uses could be extended in a similar manner for GitLab. See also JENKINS-34396 Is Perforce scm supported by the Pipeline plugin? As a SCM source for discovering a Jenkinsfile, not at this time. The P4 plugin does provide some p4 steps which can be used in a Pipeline script however, see here for documentation. Is Mercurial supported with multibranch? Yes, it is. Can Jenkinsfile detect when it’s running against a pull request vs an approved commit, so that it can perform a different type of build? Yes, via the env variables provided in the DSL scope. Using an if statement, one could guard specific behaviors with: if (env.CHANGE_ID != null) { /* do things! */ } Let’s say I’m building RPMs with Jenkins and use build number as an RPM version/release number. Is there a way to maintain build numbers and leverage versioning of Jenkinsfile? Through the env variable, it’s possible to utilize env.BUILD_NUMBER or the SCM commit ID, etc. Love the snippet generator! Any chance of separating it out from the pipeline into a separate page on its own, available in the left nav? Yes, this is tracked in JENKINS-31831 Any tips on pre-creating the admin user credential and selecting plugins to automate the Jenkins install? There are various configuration management modules which provide parts of this functionality. I’m looking at the pipeline syntax (in Jenkins 2.0) how do I detect a step([…​]) has failed and create a notification inside the Jenkinsfile? This can be done by wrapping a step invocation with a Groovy try/catch block. See also JENKINS-28119 User Interface/Experience Is the user experience same as before when we replace the Jenkins.war(1.x to 2.x) in an existing (with security in place) installation? You will get the new UI features like redesigned configuration forms, but the initial setup wizard will be skipped. In its stead, Jenkins will offer to install Pipeline-related functionality. Is it possible to use custom defined syntax highlighting ? Within the Pipeline script editor itself, no. It is using the ACE editor system, so it may be possible for a plugin to change the color scheme used. Can you elaborate on what the Blue Ocean UI is? Is there a link or more information on it? Blue Ocean is the name of user experience an design project, unfortunately at this point in time there is not more information available on it. General How well this integrate with cloud environment? The Jenkins controller and agents can run easily in any public cloud environment that supports running Java applications. Through the EC2, JClouds, Azure, or any other plugins which extend the cloud extension point, it is possible to dynamically provision new build agents on a configured cloud provider. Are help texts and other labels and messages updated for other localizations / languages as well? Practically every string in Jenkins core is localizable. The extent to which those strings have been translated depends on contributors by speakers of those languages to the project. If you want to contribute translations, this wiki page should get you started. Any additional WinRM/Windows remoting functionality in 2.0? No Is there a CLI to find all the jobs created by a specific user? No, out-of-the-box Jenkins does not keep track of which user created which jobs. The functionality provided by the Ownership plugin may be of interest though. Please consider replacing terms like "master" and "slave" with "primary" and "secondary". "slave" has been replaced with "agent" in Jenkins 2.0. Updated 2020-09-18 : The term "master" is being replaced with "controller". We’ve been making tutorial videos on Jenkins for awhile (mostly geared toward passing the upcoming CCJPE). Because of that we’re using 1.625.2 (since that is what is listed on the exam), but should we instead base the videos on 2.0? As of right now all of the Jenkins Certification work done by CloudBees is focused around the Jenkins LTS 1.625.x.

Vous êtes développeuse ou développeur, vous avez envie de découvrir le projet Jenkins de l’intérieur, en bricolant sur un sujet qui vous intéresse, lisez la suite ! Mercredi 9 mars, le Toulouse Jenkins Area Meetup organise à Toulouse un Hackergarten Jenkins, occasion idéale pour faire ses premiers pas dans la communauté assisté(e) d’un contributeur au projet. Hackergart quoi ? Hackergarten est un mot qui provient de la contraction des mots Hacker et Kindergarten, ce dernier étant le mot allemand qui désigne en gros l’école maternelle. Comment ça va se passer ? En partenariat avec le Toulouse Java User Group (c’est sur ce lien qu’il faut s’inscrire), nous nous donnons rendez-vous à partir de 18h30 dans les locaux de l’Epitech Toulouse, chacun avec son ordinateur (non fourni), et on commence à jouer. Et c’est bien sûr gratuit et ouvert à tous. Un tableau trello a été initialisé pour tenter de s’organiser un peu. La liste des choses à faire n’est pas du tout figée, et les idées sont les bienvenues. Les commentaires sont ouverts à tous, et l’accès sera donné à quiconque en fait la demande (façon communauté Jenkins :-)). Goodies ! Grâce à l’aide de CloudBees, on a pas mal de goodies à offrir : stickers, badges, t-shirts et bobble-heads ! Les Bobble Heads Jenkins Nous en avons 2 ! Et ceux-ci seront offerts au deux premiers participants à voir leur pull-request envoyée pendant la soirée mergée . Que faire pour (se) préparer ? Si vous n’en avez pas, créez-vous un compte pour les services suivants : Jenkins GitHub Trello Au niveau machine, idéalement, vous avez : Git et Maven bien installés Docker installé (natif sous Linux), ou via Docker Toolbox pour les autres OS Des informations plus précises seront normalement données très bientôt aux inscrits via meetup quant à la préparation des machines. Quel(s) langage(s) faut-il connaître ? Idéalement, puisque Jenkins est écrit en Java, il serait souhaitable que vous connaissiez au moins les bases. Toutefois, même si par exemple vos compétences sont plutôt côté Web, il y aura aussi des choses à faire, que ce soit jouer avec le nouveau site en préparation, ou ajouter une page web câblée sur certains fichiers json des statistiques. Connaître au moins les bases de Git sera un gain de temps, mais ce n’est pas indispensable. Récapitulatif locale=fr-FR">Pour s’inscrire (indiquez Jenkins à la question posée au _RSVP) le tableau Trello dédié aux activités de la soirée (demandez l’accès !) Cf. ci-dessus pour les choses à installer sur votre machine N’hésitez pas : l’ambiance est accueillante, et on offre les pizzas !